Author Topic: Guild member stuck at anonymous (Read 7082 times)

Poonjab · « **on:** July 14, 2009, 07:09:20 pm »

I have a guild member that is stuck with Anonymous access and I can't seem to get him unstuck from that.

I have tried manually adding him, deleting him and re-adding him, deleting him and having him talk in guild to be re-introduced to the bot, but it always shows his access as anonymous no matter what I do.

He did change his toon names at one point in time, but I'm not sure if it happened before or after that.

What is the best way to get rid of a user from the bot and have him re-introduced to the bot via guild chat?

Thanks in advance.

Khalem · « **Reply #1 on:** July 14, 2009, 07:19:28 pm »

Are there any errors in the console when adding or removing him?

My first suspect would be that there is a duplicate entry in the users table somewhere, probably related to his name change.
There really should be an error in the console though.

You might need to inspect the table manually using sqlyog or another database tool. I would be interested in knowing what you find out as well so it could be prevented in the future.

Poonjab · « **Reply #2 on:** July 14, 2009, 11:03:27 pm »

I'll see if I can generate an error tonight.

I did go thru last night in the botname_users table and deleted all rows with names of his toons... Hopefully I didn't screw anything up too bad there, but knowing me, I probably did, or there's something else I should be doing.

clashbot · « **Reply #3 on:** July 15, 2009, 02:11:19 am »

there is a bug going around with rerolled toons not showing up properly that will cause the anonymous bug. Check funcom's char lookup on him also and verify that it is displaying the correct information, otherwise it's not in the bot, but in funcom's char xml

Poonjab · « **Reply #4 on:** July 15, 2009, 07:13:48 pm »

He's working now. I think deleting his info from the user table and after he re-logged and talked in guild finally got him back to normal.

Now I just gotta figure out how to remove people from security groups when I decide they should have lower access.