TrinityCore / TrinityCore/TrinityCoreCustomChanges
3.3.5-passive_anticheat World database autoupdater faulted
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 83
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
Description:
Well I guess we have some minor problem if you try to remove completely world database, the server is trying to repopulate it but will end with this error:
Worldserver log
Could not prepare statements of the World database, see log for details.
DBErrors log:
In mysql_stmt_prepare() id: 72, sql: "SELECT function_name, enabled FROM lua_private_functions"
Table 'world.lua_private_functions' doesn't exist
Current behaviour:
I guess the server expect that table lua_private_functions to be already inported in world.
I know we can just copy the world.anticheat in updates/3.3.5 but maybe we can move it there forever since it's mandatory.
Expected behaviour:
World database shoud be populated and server start normally.
Steps to reproduce the problem:
- Drop world database
- Start server again and wait for it to finnish his attempt to start
- notice
Branch(es):
TrinityCore rev. 180a0adbe4a9+ 2024-02-12 01:27:33 +0000 (3.3.5-passive_anticheat branch) (Win64, RelWithDebInfo, Static) (worldserver-daemon)
TC rev. hash/commit:
TrinityCore rev. 180a0adbe4a9+ 2024-02-12 01:27:33 +0000 (3.3.5-passive_anticheat branch) (Win64, RelWithDebInfo, Static) (worldserver-daemon)
TDB version: TDB 335.24011
Operating system: Windows 11 x64
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the world database updater and the updates/3.3.5/world.anticheat update, then trace preparation of the lua_private_functions query shown in the DBErrors log. Reproduce the failure by dropping the world database and restarting; done means the database is repopulated and worldserver starts normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100