BeBot - An Anarchy Online and Age Of Conan chat automaton
Archive => Age of Conan Archive => AoC 0.6 support => Topic started by: magnusll on May 14, 2010, 02:50:30 pm
-
Subject says it all more or less. Apparently the bot is unable, for some reason, to find out the online/offline status of its members.
No idea if it can be related, but I always get the message:
[ERROR] [AOChatWrapper_Core] I was unable to get the user id for user: <bot username>
at bot restart. Tried to create a new user and start a new bot using it, and still got the exact same problem though.
Any clue?
-
My bot says the same when loading, but else it's working fine so thats not where your problem is. Are you sure you've logged your bot character in and spoken in guild chat before starting it?
-
Yes, the bot has normal access to the guild channel. For example, it will listen to commands given in guild chat and reply normally. But the "online" function seems permanently disabled; the table will always stay empty.
It almost looks like it's not receiving the login notifications from the chat server.
-
Does it announce players when they come online? Did you set the bot to automatically add new players?
The bot maintains a buddy list as well, what you could do is log in as the bot (stop the bot, start aoc client etc) and check if there are people in it's buddy list.
-
Ok... I have no idea how, but I got the one on the new character to work. It is now normally marking people as online.
Only obvious difference I can see is the lack of "not on notify" messages on characters' status changes in the log, which I take it indicates the fact the old bot was not sending notifications to whichever module is tasked with tracking online status. Is there any specific setting handling this? It's weird since I didn't touch any of the defaults.
-
not on notify means it's not announcing them, it's a setting you can change (somewhere, don't have access to my bot at the moment)
anyway it all works now so good :)
-
The setting can be changed via "/tell yourbot notify on playername"
-
This thing had happened to Immortalbot yesterday. I thought my dedicated server upgrade corrupted MySQL database until I ran into this thread. Luckily, I back up my database two days ago.
I troubleshooted for few minutes and it has been fixed with my last solution:
I experimented by creating a new database, restore it using the file I backed up, change MySQL.php to the new database name and it had been fixed. I lost some members that was added automatically but I should get everybody back by the end of this week.
Other than that, it's flawless!