-
-
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 Riding Speed increases Druid Flight Forms #16761
base: master
Are you sure you want to change the base?
Conversation
tested
Normal mount
Please review and tell me if this is correct behaviour or not |
Yes, enchant, spurs and carrot should stack |
corrected the above then <3 |
…rothcore-wotlk into Druid_Flight_Forms
Conflict |
Can you please resolve the conflicts again |
Thanks for the update! I'm using Carbonite right now level 70 tauren druid in "swift flight form" unequipped equipped If I understand correctly, the speed should be 280% even when "Riding Crop" is equipped? Right now to me it looks like this PR does not have the desired effect, can you please check or give a hint what's going wrong on my side? Thanks! |
The Riding Crop is working with or without changes. However, the carrot on a stick and mithril spurs need modification Interesting fact: flying mount 305% and swift flight form 295% |
Looks like CI is broken right now |
So what's the state of this PR now? Ready to be tested again? |
Conflicts |
What's the status for this ? if it's not ready can we label it differently ? |
TBH I don't like DBC edits that edit effect types, aura types etc. Always feel like a big hack |
the effect is affecting the speed of other flight assemblies. i don't know what to do |
There have been changes made in this PR forth and back but there's no real "this is it - please review and test" state in this PR. I would suggest closing it for now. Please feel free to open a new PR if you've found a viable solution for this issue. |
When comparing Mithril Spurs 59916 (no bug) with Riding Crop 48383, the DBC effects differ which explains the bug. Imo the DBC is wrong, or the below is using the wrong
relevant core, handling looks correct
|
Changes Proposed:
Issues Addressed:
SOURCE:
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.