Disallow character creation with same name as existing bot

[Toony]

I've had a user create a character with the same name as a previous users bot, no big deal apparently until they both entered the same zone, this caused them both to crash.

I'm pretty sure multiple bots can't have the same names already, but it seems like character creation doesn't check against existing bot names, any known fixes either direct or workarounds?

--edit-- turns out this seems to have actually caused zone.exe to crash as well

Thanks

[FievelMousey]

This been a bad issue for ages wow and it yet not fixed

[irongut_av]

I use an event (in HeidiSQL, right click your eqemu database, select Create New->Event). It runs every 4 hours in MySQL, which appends a value onto a bot name if that name exists on the character_data table. This would probably work better as a trigger for the character_data table, but I've got no experience working with those.



BEGIN
update bot_data
inner join character_data on bot_data.name = character_data.name
set bot_data.name = CONCAT(bot_data.name, "A");
END


I also had to enable the global event scheduler in MySQL using root:


SET GLOBAL event_scheduler = ON;



Make sure you set a start time and don't have it expire, so it runs each time period you choose. This isn't a perfect fix, but will rename bots in the DB.

[Uleat]

I was on sabbatical when this thread was started...

I'll add it to my list.

[Huppy]

I remember this issue from long before this thread, but I suppose a permanent fix would involve two sides to it.

Bot existing on new character creation, or character existing on new ^botcreate. Name not available either way ?

[Uleat]

Pretty much :)

I'll have to make a script to fix issues as well..a one-time pass with a client bias.