josh
b853b3ae06
Shipped patches:
playerbotv2_core_hooks.patch — stock TrinityCore master
playerbotv2_core_hooks.thordekk.patch — ThordekkCore
SQL applied at module init by PlayerbotMigrationMgr:
sql/playerbot_v2/0000_playerbot_shared_bootstrap.sql — creates playerbot
shared DB + tables (handcrafted_road, playerbots_names,
playerbot_dungeon_routes, playerbot_nav_links,
playerbot_v2_world_metadata)
sql/playerbot_v2/0001..0016*.sql — character DB tables
SQL auto-applied by TC DBUpdater:
sql/updates/auth/master/
sql/updates/characters/master/
Manual fallback:
sql/playerbot/playerbot_bootstrap.sql
Static data (manual):
src/modules/PlayerbotV2/sql/shared/
src/modules/PlayerbotV2/sql/world/
Includes: Log.h, SpellAuras.h (PlayerbotAPI), Position.h (PlayerbotHooks)
1.1 KiB
1.1 KiB
Playerbot V2 — SQL migrations
Per v2/SCHEMA.md. Migration files in this directory are numbered, append-only, and idempotent. Run by Persistence/PlayerbotMigrationMgr at module init.
For full setup instructions (schema creation, config, world fixes) see
v2/INSTALL.md.
Order
Applied in ascending numeric order; each file records itself in
playerbot_v2_schema_version. Current set:
0001_init.sql— schema_version + core tables (account, character, personality, preferences, population_target)0002–0014— owner/squad control, talent builds, population columns, guild metadata, world metadata, leveling zone, fleet vitals, archetype, craft orders, stuck-objective ledger0015_name_pool.sql— the curated ~107k-row random bot name pool (playerbots_names), shipped with use-state reset so a fresh install starts with the whole pool available
Discipline
- Never edit a numbered migration after it ships. Add a new one to amend.
- Each migration is self-contained: no cross-file dependencies on application order beyond numbering.
- Reversibility documented in the file header.