Thought i'd try my luck at this one. Downloaded bebot 2.9 and coded/tested a few hours ago. So I have only tested !is and !member (which does not work due to FC also having integer probs).
Note a: Problems might occur depending on your MySQL version and setup. (Strict mode)
Note b: All Character id's are now passed as strings, so if you like to define variables in (ie: $id = (int)$this...) your scripts it will have unintended results upon meeting an id > 2^32

Another thread, with the same theme already exists. This is very different code tho and i did not want to step on the other posters toes.

Solved the problem with new users :-)

Tower attacks get parsed somewhat strangely now tho:

[2006-10-27 05:23:02]   [GROUP] [MSG]   [All Towers] -1: ~&!!!&r!5b/RR!!!8S!!!!"
s"The Society for Rollerrat Crueltys?JeekR!!!8S!!!!"s¶Ancarim Iron LegionsAvalon
i!!!Asi!!!IC~

I just downloaded the 2.9 version and slapped this together from it's AOChat.php, for the tower message to be parsed as such the username must be "0" the towermsg posted by jjones is from "-1" so it won't get parsed.

edit: Fixed version posted further down.

Ah, a small problem occured in get_uname thats called on incomming group messages - it evaluated the $user "0" as a numeric and then tried to get the associated username, instead it should just return "0" as the uname, which it is.
Should be fixed now.

Edit: New version on page 2

I'm getting an SQL error on INSERT INTO members, with the new toons;

Out of range value adjusted for column 'id' at row 1

id = INTEGER in the table.. should I modify it?

I think I've fixed it by changing the ID column in table Members to Unsigned Integer..  seems to be working fine atm

More than likely the real issue here is that some people are ending up with negative character id's now in funky lengths and seems to be unpredictable from what I've seen.  Should be easily fixable with just a change of type on the table as noted above.

More than likely the real issue here is that some people are ending up with negative character id's now in funky lengths and seems to be unpredictable from what I've seen.  Should be easily fixable with just a change of type on the table as noted above.

The bot ends up with negative id's because the new players have id's higher than 32bits signed, which is the only integer type available in php, this will then overflow into the negative.
This is 100% predictable behavior and can be reversed, only you can't use floats, php's other numeric type, as array keys since php will round and convert that to an integer. The only type left then are strings...