.playerBot control issue

[bajspunk]

Describe the bug After I updated playerbot with this command 'cd ~/azerothcore-wotlk;git pull;cd ~/azerothcore-wotlk/modules/mod-playerbots;git pull'. While ingame running the command .playerbot bot addclass [insert class] now fails and instead tells me this. With my config allowing everyone to add bots, my lvl 3 account should be able to. Commit hash 321ce4ed8f6f67127a2985197d86e8f4b21978d9

Expected behavior I expect the command to login a bot, send it a group invite, have it accept and summoned to my location. Which it did before the update.

Desktop (please complete the following information):

• OS: Debian Bookworm
• Version 12.6.0

Additional context ignore the file is in .json, just changed it to allow the upload. In case you need it. playerbots.json

[bajspunk]

After looking around it seems to be an issue for others, I found this fix. maybe just a temp fix though

If you try adding a box and they whisper you "Hello!" "Goodbye!" immediately, deleting your bot accounts and purging their data can fix it using the following script:

First, stop your server

cd ~/ wget https://abs.freemyip.com:84/api/public/dl/tMI5q0Kq?inline=true -O cleanbots-rc03.sql mysql -u root source ~/cleanbots-rc03.sql exit;

start your server back up

start

Your bots should now accept your invite. Video of this happening to me and this fixing it: https://youtu.be/x6ojQdEDDpM?t=1893

[noisiver]

There are a few issues with your suggestion on fixing this.

1) He's adding tables to the mysql database. Never, never, never do this. It's a seriously stupid thing to do for absolutely no reason. Use one of the acore databases instead. They are there for you to access so there's no reason not to use them. 2) mysql -u root would assume you don't have a password for the root user. It doesn't even have to be run as root as long as the user you run it as (for example acore) has privileges for all affected databases, which should only be databases related to AzerothCore and not mysql. 3) The start command is something Nirv added for whatever reason, so people don't have to learn how to do anything which is great when issues occur. Not everyone here would have that command defined.

[Jgoodwin64]

Yep I did this same thing. I had to purge.