BeBot - An Anarchy Online and Age Of Conan chat automaton

General => Feedback and Suggestions => Topic started by: yueee on February 01, 2006, 03:44:03 pm

Title: Bebot for rk3 fix
Post by: yueee on February 01, 2006, 03:44:03 pm

just a tiny fix since rk3 uses a different port than the other servers, no idea if i missed a post about this issue. if thats the case ignore the post.

Title: Re: Bebot for rk3 fix
Post by: Glarawyn on July 14, 2006, 07:18:48 am

I haven't looked at yueee's fix, but the needed edits are quick.

Find line 127 in bot.php, and update the switch statement as below:

Old:

Code: [Select]

        // Get dimension server
        switch($this -> dimension)
        {
            case 0:
                $server = "chat1.d1.funcom.com";
                break;
            case 2:
                $server = "chat3.d1.funcom.com";
                break;
            case 3:
                $server = "chat.dt.funcom.com";
                break;
            default:
                $server = "chat2.d1.funcom.com";
        }

New:

Code: [Select]

        // Get dimension server
        switch($this -> dimension)
        {
            case 0:
                $server = "chat1.d1.funcom.com";
                $port = 7012;
                break;
            case 2:
                $server = "chat3.d1.funcom.com";
                $port = 7012;
                break;
            case 3:
                $server = "chat.dt.funcom.com";
                $port = 7013;
                break;
            default:
                $server = "chat2.d1.funcom.com";
                $port = 7012;
        }

Under the switch, make the following change.

Old: 

Code: [Select]

$this -> aoc -> connect($server);New:

Code: [Select]

$this -> aoc -> connect($server, $port);

Title: Re: Bebot for rk3 fix
Post by: Khalem on July 14, 2006, 06:40:42 pm

I could have sworn i fixed this already, but bleh.

Added to SVN.

Title: Re: Bebot for rk3 fix
Post by: Glarawyn on July 14, 2006, 07:31:57 pm

Quote from: Khalem on July 14, 2006, 06:40:42 pm

I could have sworn i fixed this already, but bleh

I ran into it with v0.2.5 so maybe changes got overwritten somewhere along the line. I've managed to do stuff like that a few times...