-
-
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/Quest) - Fortunate Misunderstandings #21074
base: master
Are you sure you want to change the base?
Conversation
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.
Newline at the end in the SQL. Fix your issue description and tells us a little more what are you doing with this fix.
Hi,
Could you please refine the steps on how to test it? Please also fix your PR matkdown. |
It's a chain quest. So you need to do this quest ID: 12540 first. Only then will the quest be released and you can talk to the NPC. |
Tested and works but I'm not sure don't think we are doing it correctly. To my understand upon completing of the escort that npc (which was stored from the previous quest if i read it correctly). He should use the "spell" that completes the quest and allows you to deliver it. For anyone testing like @Exitare which was confused and I can't blame him for the lack of proper steps to test.
|
Yes, you are correct. The correct thing was for the NPC to cast a Spell. However, for some reason I couldn't identify this problem. I did some tests and the Spell needs to be Clicked twice to work, which is why the Cast doesn't work. I don't know if that's the reason. So I modified the code so that at the end of the escort the Quest is completed, just like many others that work the same way. The only difference is that the NPC no longer casts and completes the Quest normally at the end of the escort. |
This is a hack. You have to fix the spell, which can be done in a spellscript with FilterTargets |
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:
After the NPC Injured Rainspeaker Oracle = 28217 is escorted to the Rainspeaker Canopy Camp. Complete the Quest Fortunate Misunderstandings = 12570.
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.