BeBot - An Anarchy Online and Age Of Conan chat automaton
Archive => Anarchy Online Archive => BeBot 0.4 support => Topic started by: Diablo on October 20, 2007, 11:05:47 pm
-
Ive notice lately members that have been removed from org are still showing up when they log on as members of the bot? Anyone notice this or is there fix i misses?
-
its mostly becouse FC db havent been updated, use helpbot or any other bot, if is same, then it is FC db, of course you can check FC website too. :D
-
When i check other bots they show they are in another org but our bots still shows wrong.
-
Same with ours, it even readds members I have kicked earlier (suddenly did that 2 days ago after person beeing "evicted" for 2 weeks) and keeps retaining them even FC's db is updated. The funny thing is that the bot -had- it correct after I kicked the former member until a few days ago by updating him not in org, then his new org, now he's suddenly back in our org in addition to the bot inviting him/notifying him of our news and letting him in our bot and I -cannot- get him removed.
-
the Database has been updated now
should of been working fine for a few days now
-
if need be ban him that will fix individual probs
-
Removed, updated, re-added to bot. Has this anything to do with the bot -constantly- loading settings from database?
-
Exact same problem we are having with all three org bots we run. Kick a few members one day bots showed they no longer members and couple days later they are back on as members. Also noticed its not updating lvls of members for up to three days.
-
Old org roster coupled with not updating levels points to problems in the XML files for me. The bot can't catch those reliably sadly.
-
Ok just noticed today an old member that left couple weeks ago and that hasnt showed up in bot just showed back up in bot today again as a member of org but ao site says they are part of other org still.
-
Same issue here.. no matter what changes I try.. is this all FC doing?
Cause a friend of mine running vhabot isn't having this issue
-
i'm having this same problem in my orgbot, for a temp fix i cleared the whois cache and it seems to have fixed it, for now
-
This is most likely an error in the code that handles the roster. I think it was introduced with either onlinedb or notify.
However this is an error not easily located. There is plenty of code that needs to be cleaned up with roster handling.
For the time being I recomend putting a ban on the player(s) and the roster handling will be reworked.
-Terje