-
-
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/Core/Quests): Fix the quest "Load'er Up" #20241
base: master
Are you sure you want to change the base?
Conversation
Move quest 11881 to the core for better scripted control and more blizzlike behavior. Closes AzerothCore issue azerothcore#20239
This PR can't be done with SAI ? |
It was previously SAI but it was broken. The summoned NPC would immediately despawn on damage taken. I also added a feature to temp summons to prevent them from inheriting their owner's speed values since this NPC in particular runs alot slower than the player. Previously, the summon would act like a warlock pet or hunter pet and match speed with the player. Additionally, there are some events that are part of this quest that are easier to handle in a script as opposed to SAI. It's working pretty damn close to the original blizzard quest now. |
Tested PR. |
WHERE `entryorguid` = 25969; | ||
-- Update creature template for NPC Jenny (25969) | ||
UPDATE `creature_template` | ||
SET `speed_run` = 1, `speed_walk` = 0.8, `speed_swim` = 0.6, `AIName` = "", `ScriptName` = "npc_jenny" |
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.
speed values are sniffed. They don't change unless you have sniffed values
@@ -2041,6 +2129,7 @@ void AddSC_borean_tundra() | |||
new npc_thassarian2(); | |||
new npc_leryssa(); | |||
new npc_counselor_talbot(); | |||
new npc_jenny(); |
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.
Use the new registry model.
RegisterCreatureAI()
After the changes does this still need testing? Also @cgrahamseven the changes asked. |
@TheSCREWEDSoftware I don't have the time right now to look into the change requested by @Kitzunu to use RegisterCreatureAI. The NPC is not a ScriptedAI. If you'd like the PR either revert it back to the previous registration or have someone else do whatever conversion is necessary. Thanks |
Move quest 11881 to the core for better scripted control and more blizzlike behavior.
Closes AzerothCore issue #20239
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.