-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
feat(Core/Conf/BG): allow battlegrounds to be more configurable (#20320) #21124
base: master
Are you sure you want to change the base?
feat(Core/Conf/BG): allow battlegrounds to be more configurable (#20320) #21124
Conversation
Don't hesitate to make a lot of comments if needed, I don"t do C++ very often |
I tested the PR. Everything else checks out |
Yes, no WorldState in WotLK for the max score XXXX/1600 for Eye of the Storm, can't find anything for that (but no problem for Arathi), so the team score frame stay the same at the top of the screen in Eye of the Storm, have checked in cmangos, trinity, etc... but simply no WorldState for this thing (have not found it), so it need client modification I suppose
EDIT: I can eventually revert this specific modification/configurable settings, but it's written in the configuration for now thats UI is not compliant/correctly sync (like that it's not a surprise for anyone modifying this param in configuration) (sorry my english is a little bit broken) |
Isnt this snippet sending an update to the client? Or is the client just not reacting to it? |
Can't confirm :/ |
Changes Proposed:
This PR proposes changes to:
Issues Addressed:
Warsong
Arathi
Alterac
Eye of the Storm
*Note:No WorldState exists for the max score in this battlefield (XXXX/1600), and I found nothing elsewhere for wotlk
so if you set the maxscore to 2000 for example
it will display scores likes 1700/1600 or 2000/1600 instead of 1700/2000 or 2000/2000, seems client related,
the problem exists only on Eye battleground (no problem in Arathi)
Strand of the Ancients
Isle of Conquest
and I don't want to make too much modifications to the existing code,
so I let it unmodified and non configurable for now
SOURCE:
The changes have been validated through:
Tests Performed:
This PR has been:
How to Test the Changes:
Tested with original & modified Warsong max flags from configuration
Tested with original & modified Arathi max capture points from configuration
Tested with original & modified Alterac reinforcements from configuration
Tested with original & modified Alterac boss death rep points from configuration
Tested with original & modified Eye of the Storm capture points from configuration
See notes above for Eye of the Storm
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.