BeBot - An Anarchy Online and Age Of Conan chat automaton
Archive => Age of Conan Archive => AoC 0.6 support => Topic started by: Runemy on September 20, 2010, 01:56:07 pm
-
I've had this one for ages and it's been a constant annoying thing. This as almost daily current online guildies are being treated as the "-1" and they can't use the bot. I have started off with a fresh database a few months ago, which made the problem go away for the time being, but now it's getting more and more frequent again. Upon a startup or rosterupdate I reccon I have approximately 30-40 -1 buddy-adds now and I can't for the love of Crom figure out why these things occur.
So, am I the only one struggling with this issue, in that case I'll just have to live with it, but if not and there are many with the same issue, can we try to find a fix? :)
-
I'm the only one having these problems?
Bollox! ^^
-
I do see the -1's but it isnot affecting any of my bot users.
-
I have the same problem. I ussally solve it with restarting the bot after rooster update. It will get back after a while and then Ill have to restart it again.
-
Probably the users that have problem are the users that deleted their char and used the same name again, same name different id. If !deluser <username> and add !member add <username> doesn't solve your problem then shutdown bot, delete the specific records from the db, log in the actualy bot char and make sure that the problematic users are not in friends list. Run bot again and try to register them by typing in guild chat or member add command.
-
I am testing out a fix for this that deletes all users with the nickname -1 every time a rosterupdate is run. I will let you know and post the code once I have had it running for a bit.
~Kyr
-
I am testing out a fix for this that deletes all users with the nickname -1 every time a rosterupdate is run. I will let you know and post the code once I have had it running for a bit.
This will replace the existing main/10_Roster.php.
You can see the difference on lines 270-276.
You can force this clean up to happen by running !rosterupdate otherwise it runs every so often on its own.
~Kyr
-
Yay! I really look forward to testing this one!
Thanks for the effort!
-
One short thing though, it seems like online also is "infected" with the -1's when it occurs. Will it make any harm if I add
$this -> bot -> db -> query("DELETE FROM #___online where nickname = '-1'");
at line 276? It shouldn't mess up anything, but better safe than sorry and all..
-
Thats a good idea. I will add to mine also. Thanks.
updated file in post above.
-
my bot went crazy when I added this. Everyone was showing up as -1.
-
That's really, really odd. The newly added code just checks if there's characters named -1 in the tables online, users and whois and deletes them if so, shouldn't cause any problems like that really.
It has saved me the work of deleting these users manually, but for some reason it still is a problem now and then. I've got no idea what triggers the bot into doing this, but I've found out that "Total radio silence" (No talk in guild chat or query's to the bot) when doing a restart of the bot helps a lot.
-
I posted asking about this problem about 12 months ago. The best reason we could come up with at the time was that it happens when FC's servers don't provide and answer to a bot name lookup. It seems to come in waves on my bot where I'll not get any problems for a few weeks and then I'll get 3 or 4 days of constantly doing manual data base edits.
I too have meant to automate the deleting of -1 but just never got round to it.
Be great to know exactly what was causing this so some error trapping could be built in. It's very annoying when it happens.
G
-
For me it happened each time one of the guild members deleted a character and created a new one using EXACT name.
My guestimate the bot gives and ID to each new added member, ID that is linked to the FUNCOM user ID, when a player deletes a character and creates a new one FUNCOM generates a new ID, ID that now is not linked to the one generated by the BOT, hence the error.
Anywho I suspect something among those lines, I might be dead wrong. :)
-
That might cause the error, but it's not the only cause. I've had it on my "main" which has had the same name since pre-release in 2008. It's nothing to do with re-naming (or rather renaming is a red herring which might cause the problem but isn't the only cause)
G
-
Yeah, same here, I've even had it on the char that's registered as the owner of the bot. Born on 17'th of May 2008. :)
It seems very random who gets it and when it happens so what's causing it is beyond me.