Author Topic: AOchat.php error (Read 2764 times)

Nytridr · « **on:** February 28, 2007, 12:13:32 am »

well I get on me server today.. it was beeping at me.. go figure.. almost sounded like my wife for a little bit... (okay enough of the pwn)

anyway like I said it was beeping.. and it has never done this before... one of the bots I run in another org was causing it.. there org towers were under attack..

Code: [Select]

AOChat ExtMsg Debug: Unknown Cat: 506 Instance: 94492169

[2007-02-27 23:06:58]   [GROUP] [MSG]   [Org. Msg.] 0: ~&!!!&r"ejKRs?Massive Can
non Turrets?Broken Shoresi!!!!:s?DancingcatsSlayer~

okay either I have a corrupted aochat.php file or something..

Aesgaard · « **Reply #1 on:** February 28, 2007, 02:06:42 am »

I got the same problems involving tower wars except that the bot doesnt beep, it just goes massive error messaging in script (I will post the exact line next time we're attacked) and the bot "crashes".

Vhab · « **Reply #2 on:** February 28, 2007, 07:16:21 am »

Likely FC changing messages around again.
The beep is caused when the raw output is send to the console and it contains a "beep" character.
I currently don't have it handy, but it would help if you use MMDB Tool (found on aodevs) to look up message 506 entry 94492169 from AO's text.mdb file and post it here.

nebhyper · « **Reply #3 on:** February 28, 2007, 04:28:13 pm »

[94492169] The tower %s in %s was just reduced to %d %% health by %s from the %s organization!

Vhab · « **Reply #4 on:** February 28, 2007, 04:57:22 pm »

aha, guess that's just not recognised by the bot.
the beep is just a side effect.
would advise the codemonkey to strip control chars from the output before sending stuff to the console.
eitherway, it's nothing you should be worried about.

Nytridr · « **Reply #5 on:** February 28, 2007, 05:57:13 pm »

yea.. didnt seem like it was causing any problems.. just thought I would bring it up.. heck I dont need something else... BEEP BEEP BEEP BEEP'ing at me.. expecially a machine!!! :)p

Vhab · « **Reply #6 on:** February 28, 2007, 06:20:42 pm »

On second thought, It's a feature to wake you up when your org is under attack!

Khalem · « **Reply #7 on:** March 01, 2007, 08:43:40 pm »

Dum dei dum.

The real solution is to fix AOChat.php to not depend on static entries but use the mmd database itself (or at least a stripped down version of it) to avoid this problem more or less completely.

It's completely harmless though, aside from the annoyance of the beeping.