Author Topic: [Org. Msg.] & LCA messages (Read 15356 times)

exxie · « **on:** May 04, 2007, 09:13:00 pm »

hi,

i noticed that bebot doesn't parse the LCA damage messages anymore. i don't know exactly since when but it's definitely a few weeks now.

all other messages in the [Org. Msg.]-channel are parsed correctly.

[GMSG][MSG][Org. Msg.] 0: Player has joined the organization.
[GMSG][MSG][Org. Msg.] 0: Blammo! Player has launched an orbital attack!

these messages as well as the kick und leave messages are being parsed but when there this a damage message the bot outputs it like that:

[GMSG][MSG][Org. Msg.] 0:

without any text. it definitely worked a few weeks ago! any ideas?

Alreadythere · « **Reply #1 on:** May 04, 2007, 09:40:45 pm »

Seeing that the tower damage was never in the AOChat.php at all I doubt that it worked before - or at least since FC changed the format to the new encoding.

For the SVN version at least it's on the todo list though

exxie · « **Reply #2 on:** June 20, 2007, 02:40:08 am »

yea. you are right.

but it has to be a limitation of bebot because it works perfect with ignbot and angelsbot.

this is from the logfile of the bot, receiving an org-message:

[2007-06-17 08:59:34] [TELL] [INC] Omnipotentus: relay The tower Simple Missile Turret in Galway Shire was just reduced to 75 % health by Lirna1 from the Unknown organization!

the bot sending the message is an ignbot:

Code: [Select]

global $sender;
if ($type == 65 AND $sender == "") {
	if(preg_match("/^the tower (.+) in (.+) was just reduced to (.+) % health/i",$args[2])) {
		$aoc->send_tell("Battlecom","relay ".$args[2]);
		$noreply=1;
	}
}

so it's definitely not a problem of the aochat-class.

Ebag333 · « **Reply #3 on:** June 20, 2007, 08:40:16 am »

the AOChat.php was customized specifically for IGN. Not sure about angelsbot.

It's not unlikely that those were added in at some point.

Khalem · « **Reply #4 on:** June 20, 2007, 02:58:03 pm »

Angelsbot looks up the strings from the AO database file directly, something which imho is a better solution than the hard coded strings we use.
This way you automatically have support for any new messages they move to the new system. All you'd need is the file from your AO install