-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(Core/Player): properly update m_usedTalentCount #20232
Conversation
fix(Core/Player/m_talents)?Issue: #20231Issue:
Expected Blizzlike Behaviour
Steps to reproduce the problem
Fix?This will give the real-time feedback on the changes instead of needing to relog? I will see if i get some time tomorrow to test this. |
Please use AC standard title: fix(Core/Player): properly update m_usedTalentCount |
Tested and tried with steps in #20231 (comment)
I got something working with this patch
|
So this PR doesnt work? |
it doesn't fix the issue |
…otlk into fix-issue-20231
Applied patch from <sogladev@gmail.com> fix-isse-20231 Co-authored-by: name <sogladev@gmail.com>
Thanks for testing and finding a working solution @sogladev . |
Tested and tried with steps in #20231 (comment) . I can successfully add talents and then reset talents ✅ codestyle fail |
Can you please address the codestyle issue so CI checks will pass |
…rothcore-wotlk into fix-issue-20231 merge with upstream
…ore#20232)" This reverts commit 593ca4d.
fix-isse-20231
Changes Proposed:
This PR proposes changes to:
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.