Skip to content

Fix current AzerothCore compatibility - #31

Open
G-kylexy wants to merge 1 commit into
gitdalisar:mainfrom
G-kylexy:agent/fix-azerothcore-compatibility
Open

Fix current AzerothCore compatibility#31
G-kylexy wants to merge 1 commit into
gitdalisar:mainfrom
G-kylexy:agent/fix-azerothcore-compatibility

Conversation

@G-kylexy

Copy link
Copy Markdown

What changed

  • synchronize PlayerUpdates.cpp with current AzerothCore while preserving the faction-free city behavior
  • replace removed cinematic, combat, weather, and visibility APIs with their current equivalents
  • update creature_template inserts for the current database schema
  • make the entry checker independent of the creature identifier column name
  • document the current-main database prerequisite and compatibility release

Root cause

The repository ships a full replacement copy of PlayerUpdates.cpp. That copy had fallen behind AzerothCore API changes, while the SQL still referenced fields removed from the current creature_template schema.

Validation

  • compared PlayerUpdates.cpp with AzerothCore main at 9f66598caa0334aa5f2a00cd3aa1b917c10c3d98; the only intentional behavioral difference is the faction-free city block
  • checked all SQL insert columns against the current AzerothCore base schemas
  • verified all 83 SQL insert statements have matching column/value counts
  • git diff --check passes

A full Windows server build was not available in this environment.

Fixes #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] can't build azerothcore with PlayerUpdates.cpp and sql files give error when importing

1 participant