-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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/C_T-SAI-GOBJ): NPC: Lady Falther'ess and Scourge Invasion Event #5787
fix(DB/C_T-SAI-GOBJ): NPC: Lady Falther'ess and Scourge Invasion Event #5787
Conversation
As stated here, I am not in favor of having a non-blizzlike patch. |
All good me and shin talked about it. I believe there is an existing game event for scourge invation in game_event. Could you link the NPC to this event @Stifler82 this way we can get it for the correct event. If the gob is supposed to be spawned, I suggest you add conditions for SAI only to execute when event is active. Otherwise add it to event spawn too. Good job with the initial work 👍 |
If it has to be part of an event, that's ok. If the intention of the developer is to spawn it even if the event is not active, it is problematic. |
Hey @Kitzunu, I just finished Fixing Now I'm tired, but tomorrow I'll make a video and show you the event with all the IDs so you can tell me what needs to be changed if necessary. |
I can't wait to test this! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Status on this? |
Changes Proposed:
Issues Addressed:
SOURCE:
Tests Performed:
Lady.Falther.ess.mp4
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.