Fix current AzerothCore compatibility - #31
Open
G-kylexy wants to merge 1 commit into
Open
Conversation
G-kylexy
marked this pull request as ready for review
July 28, 2026 12:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
PlayerUpdates.cppwith current AzerothCore while preserving the faction-free city behaviorcreature_templateinserts for the current database schemaRoot 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 currentcreature_templateschema.Validation
PlayerUpdates.cppwith AzerothCore main at9f66598caa0334aa5f2a00cd3aa1b917c10c3d98; the only intentional behavioral difference is the faction-free city blockgit diff --checkpassesA full Windows server build was not available in this environment.
Fixes #27