-
-
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
fix(DB/Scripts): Reset Scourgelord Tyrannus encounter state #21057
Conversation
Fixes #15824 |
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.
Match the SQL Standards
flags_extra
=flags_extra
| 1073741824
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.
Now we just need to wait for someone that has cpp knowledge to review the cpp line.
its one line of code and its alot better than the original hack fix that was applied. I worked on this project way before more people did. Ive made modules that are still being used - Talamortis |
@@ -0,0 +1,2 @@ | |||
-- Remove HARD_RESET flag while retaining IMMUNITY_KNOCKBACK | |||
UPDATE `creature_template` SET `flags_extra` = `flags_extra` | 1073741824 WHERE `entry` = 36658; |
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.
Now with your comment added I think that the sql query currently is not doing what you intended to do.
Right now it's only setting the knockback flag (which was probably already set before?)
But you wanted to remove another flag instead - so please update this to actually remove that other flag.
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.
Sorry about that, changed to newer syntax forgetting bitwise operation
@@ -0,0 +1,2 @@ | |||
-- Remove HARD_RESET flag while retaining IMMUNITY_KNOCKBACK | |||
UPDATE `creature_template` SET `flags_extra` = `flags_extra` &~ (2147483648) WHERE `entry` = 36658; |
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.
He should despawn on evade, so this is wrong
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.
It's definitely a hack on the current hack that exists, but seems to at least fix (at the moment) the boss not "reseting" if players die at him. Think the logic is that because line 100 pInstance->SetData(DATA_TYRANNUS, NOT_STARTED); in reset() sets to not even started (soft reset ish?); the HARD_RESET must not happen. Perhaps you have more thoughts @Talamorts1
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.
He should despawn on evade, so this is wrong
where is your evidence of this? this Flag was applied in a previous "Fix",
if this is the case then you need rework your instance script to spawn npc if event is not done and creature is not in instance.
I will be addressing the respawn issue in another PR. |
Testing another fix now. Ill keep you updated. |
@Talamorts1 As I said, I am already working on this |
Thanks @blinkysc for submitting this PR. @Talamorts1 as mentioned by Nyeriah they would be addressing the issue so there's no need in over-laping work. If you think there other issues that you could resolve be free to submit a PR. But the issue mentions someone fixing it, ask them first if they are still working on it, otherwise is wasting everyone's time :) |
This comment was marked as off-topic.
This comment was marked as off-topic.
Tyrannus isn't a permanent spawn. So that would never work |
I've marked your comment as off-topic @Talamorts1 if you want someone to test your fixes or you have fixes open your own PR. |
na im good, this is why i stopped helping in the first place peace out ^.^ |
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.