[Uleat]

I'm not sure on that AA's issue..especially since the owner of that thread acknowledged that he didn't have the renamed table. (He probably had an error that he didn't catch.)


On the bot issues, that '9000' script is designed to be an initial schema loader as well as a conversion script.

If you have an existing bots database, then the new schema will be created and the old data imported.

If you have an existing database with no bots schema, then there is no need to run the old 'load_bots.sql' before applying the 9000 update. You will just create unneeded and
unused tables in your database. (That's why it has been moved to the deprecated folder.)


I know there are issues with applying the 9000 script in some cases. I'm not 100% why..but, it may be related to individual server settings - such as 'INNODB_STRICT_MODE'
being set to 'ON.' If that's the case, I can set that on a per-session basis..but, I'm waiting on a reply from a couple of people before I make that change.

What I would do is verify the actions of the script. By that, I mean double-check that all of the new tables were created, the two functions and the four views.

If they do not exist, you can basically run each of those queries manually to fulfill the update requirement.

Just follow the flow of the parent script, minus creating the actual 'LoadBotsSchema' procedure.

- Create the new table
- Import data from the old table (if it exists)
- Rename the old table (if it exists)

Then add the two functions..and finally, the four views.


If done manually, you will also need to check the `db_version` table to see if you have an existing `bots_version` column.

If not, then just create another column with the same criteria as the `version` one - naming it `bots_version,` of course.

Then set that to '9000.'

(If you want to troubleshoot the script, you can set `bots_version` to '0' and it should re-run when using 'eqemu_update.pl'.)


That should bring you up to date for bots.

If you're still having problems, just post back or pm me.