-
-
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/OPvP): Halaa Mechanics not working properly #15634
Conversation
Halaa mechanics are not working like blizzlike Closes azerothcore#14355 Closes chromiecraft/chromiecraft#4642 Co-authored-by: Gultask Author: Valdifer
Right now it is working without bugs and AIs are ok |
That is sniffed |
Might be the parser or maybe an incomplete sniff, but here's what I could find in a 45854 packet:
|
Cmangos has it at 0 |
OregonCore and TrinityCore has the same values as AC (As expected) EDIT: Well, if we use that sniffed data, we don't get anymore the ghost guard |
I need someone test it and tell me what need to change, it has been done since the last update |
#include CreatureScript.h |
I deleted because i thought it wasn't necessary :/, older version didn't had it, prolly something changed in an update, well adding it again and lets see |
Update to select max GUID from creature
Anyone? D: |
@azerothcore/developers please have a look at this @Valdifer apologies for the delay and thanks for contributing |
Thanks you guys for support me and teach me new things :), i will try to do my best, if something required a review tell me |
Will test this this weekend |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have made pretty generic reviews, and not pointed out every occurence of things. Go through the entire file and check for issues I mention in my review. Also check https://www.azerothcore.org/wiki/cpp-code-standards
It's way better than the first draft though.
Changed to 40 GUID consecutive
@elthehablo how testing going |
Did some tests:
However:
This means I wasn't able to test the following yet:
|
@@ -1239,6 +1239,7 @@ enum AcoreStrings | |||
LANG_OPVP_NA_CAPTURE_A = 10026, | |||
LANG_OPVP_NA_LOSE_H = 10027, | |||
LANG_OPVP_NA_LOSE_A = 10028, | |||
LANG_OPVP_NA_DEFENSELESS = 10074, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Surely these aren't necessary? They do exist in broadcast_text
.
- follow-up to PR azerothcore#18170 to fix the remaining guid conflicts of PR azerothcore#15634
This PR features pure delete-by-GUID sql statements that would usually never get merged, but it seems that the CI doesn't care. Merging this PR as-is resulted in GUID conflicts from which half almost went unnoticed. Can we please try not to repeat something like this - it just hurts to get the own work overwritten like this and then only partially fixed. |
CI can't catch that particular case. But with enough RegEx we could probably improve it. |
At least the CI would have failed if the DELETE-statements would have included the "AND ID IN (...)" condition as the GUIDs were already taken with other IDs, or would it still have passed |
Halaa mechanics are not working like blizzlike
Closes #14355
Closes chromiecraft/chromiecraft#4642
Co-authored-by: Gultask
Author: Valdifer
Changes Proposed:
Issues Addressed:
SOURCE:
Tests Performed:
How to Test the Changes:
Known Issues and TODO List:
Capture area has to be more small(Not anymore due i don't remember how it was in Vanilla)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.