Author Topic: Lasted SVN just pulled today.. (Read 9002 times)

Nytridr · « **on:** May 04, 2008, 02:35:23 am »

I started messing around with the lastest svn again today, after being away from everything for a few months, and all I can say is that is is looking really good, and you all have done some major changes..

ok the only bug I have found in the whole process so far is,

Code: [Select]

Rsbot1 [2008-05-04 00:30:03]    [LOGIN] [RESULT]        OK
Array
(
    [0] => Array
        (
            [id] => 52
            [name] => IRC-Connect
        )

)
Rsbot1 [2008-05-04 00:30:04]    [CORE]  [INC_GANNOUNCE] Detected org name as: Cl
an (name unknown)

Found the problem with this one.. it is cause I still had $guild_name set in *.bot.conf so with the bot.conf fixed I am left with the following.. basically not detecting the org name that the bot belongs to.

Code: [Select]

Rsbot1 [LOGIN]  [STATUS]        Logging in
Rsbot1 [LOGIN]  [RESULT]        OK
Rsbot1 [CORE]   [INC_GANNOUNCE] Detected org name as: Clan (name unknown)

good job everyone.

Nyt

Alreadythere · « **Reply #1 on:** May 05, 2008, 06:44:53 am »

The org name is only set if a character logs into AO with a full client. Pure chat connections don't set the org name. The name is cleared whenever there are no chat connections online in the org.

To get the correct name you have to have a character of the org log on using the normal AO client, then start the bot. As soon as the bot is started the name is kept until all characters in the org leave chat again.

Nytridr · « **Reply #2 on:** May 05, 2008, 06:53:35 am »

Ok either i am lost on this part or something. Isnt the bot still set to only listen to guild chat if the org name matchs the org name of the bot? if these two do not match then it will not see commands in org chat. Wouldnt having someone log in then starting the bot defeat the ease of running a bot? because before you had to set it in the conf file the name of the org for the bot to listen to org chat.

If you dont mind could you clarify this for me a little? Maybe I missed something when looking at all the updates.

Nyt

Alreadythere · « **Reply #3 on:** May 05, 2008, 09:24:54 am »

The bot now reads the org name out of the group announcement packets of the AO chat protocol. If the org name is not set on the chat-server, the bot can still listen to the org chat channel, as that still exists. It simply can't read the correct name unless someone in the org logs into the game for real.

The new way is actually easier for bot users now. Before the auto-detection the bot wouldn't listen to chat in the org channel unless the name was set correctly in the Bot.conf AND the on the chat server, which requires a game logon as said. Now it's possible for pure chat user to use the bot in the org channel right from the start of the bot on. You just won't see the correct org name, instead the generic Clan (name unknown). Which is used by the bot for input and output until the org name on the chatserver is set correctly. From then on it will use the correct org name automatically, without any need for further notification. Even a change of the org name won't break reactions to org input anymore, the bot will automatically change the name of the channel it listens to.

Nytridr · « **Reply #4 on:** May 05, 2008, 10:34:34 pm »

ok I think I understand. I appreciate it. Basically it will listen to the org channel reguardless if the name is known or not, and once someone logs on then it will get the org name.. ok got it.