feat(Core/Scripting): OnPlayerResurrect allow changing of applySickness#25353
Open
sogladev wants to merge 2 commits intoazerothcore:masterfrom
Open
feat(Core/Scripting): OnPlayerResurrect allow changing of applySickness#25353sogladev wants to merge 2 commits intoazerothcore:masterfrom
sogladev wants to merge 2 commits intoazerothcore:masterfrom
Conversation
allow modification of `applySickness` to allow/disallow core application of Rez Sickness
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the player resurrection scripting hook so scripts can control whether the core applies Resurrection Sickness, enabling modules to opt-out of the default sickness behavior.
Changes:
- Changed
OnPlayerResurrecthook parameterapplySicknessfrombooltobool&so scripts can modify it. - Updated the
PlayerScriptvirtual method signature accordingly. - Updated the
ScriptMgr::OnPlayerResurrectimplementation to propagate the reference through hook dispatch.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
src/server/game/Scripting/ScriptMgr.h |
Updates the ScriptMgr hook signature to take bool& applySickness. |
src/server/game/Scripting/ScriptDefines/PlayerScript.h |
Updates the PlayerScript virtual hook signature to take bool& applySickness. |
src/server/game/Scripting/ScriptDefines/PlayerScript.cpp |
Updates ScriptMgr hook implementation to pass applySickness by reference through CALL_ENABLED_HOOKS. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Changes Proposed:
This PR proposes changes to:
allow modification of
applySicknessto allow/disallow core application of Rez Sicknessazerothcore-wotlk/src/server/game/Entities/Player/Player.cpp
Line 4425 in f8c5c9a
mod-ale
AI-assisted Pull Requests
Important
While the use of AI tools when preparing pull requests is not prohibited, contributors must clearly disclose when such tools have been used and specify the model involved.
Contributors are also expected to fully understand the changes they are submitting and must be able to explain and justify those changes when requested by maintainers.
Issues Addressed:
SOURCE:
The changes have been validated through:
Tests Performed:
This PR has been:
How to Test the Changes:
Known Issues and TODO List:
How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].
You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).
For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.