5 - Druid flight form not found
What steps will reproduce the problem?
1. Log in on a druid in a flyable area
2. Click the button/hit the keybind
3.
What is the expected output? What do you see instead?
A random ground mount is selected
What version of the product are you using?
2.5.88-release
Do you have an error log of what happened?
none
Please provide any additional information below.
| User | When | Change |
|---|---|---|
| LordFarlander | Thu, 04 Dec 2008 21:44:37 | Changed status from Fixed to Verified |
| LordFarlander | Wed, 22 Oct 2008 02:17:06 | Changed status from Started to Fixed |
| LordFarlander | Thu, 16 Oct 2008 15:06:34 | Changed priority from Medium to High |
| LordFarlander | Thu, 16 Oct 2008 15:06:19 | Changed status from New to Started |
| dwex | Wed, 15 Oct 2008 19:06:36 | Create |
- 7 comments
- 7 comments
Facts
- Last updated on
- 04 Dec 2008
- Reported on
- 15 Oct 2008
- Status
- Verified - QA has verified that the fix has worked.
- Type
- Defect - A shortcoming, fault, or imperfection
- Priority
- High - Strongly want to resolve in the specified milestone.
- #7
dwex Tue, 21 Oct 2008 22:20:13Need to replace instances of 'FlightFormDefault' with 'profile.FlightFormDefault' in Coconuts:GetStateBasedOnModifiers(). Then it works right.
- #6
LordFarlander Tue, 21 Oct 2008 15:29:52This should be fixed now. I need to do more testing to verify.
- #5
dwex Mon, 20 Oct 2008 22:10:20FYI - as a test, I changed:
to
in Coconuts:GetStateBasedOnModifiers() and this seems to work right on my druid and non-druids. That's not a real fix, but a confirmation that the logic is otherwise sound.
I'd also suggest adding forms to the list of available mounts (the printed list); when I started debugging this, I had to add debug-prints to make sure Flight Form was being detected at all.
- #4
dwex Mon, 20 Oct 2008 15:35:23Thanks. This is the one thing keeping me from using Coconuts. An excellently-designed addon, with a good mix of simple defaults and complex config for those who want to "play".
- #3
LordFarlander Mon, 20 Oct 2008 15:14:13Thank you for looking into this. I have time now to look at this (mount issues took presidence I'm afraid) You are correct that for flight forms, it should default to the form and not the mount. :) Or there should be an option to do so (this is what I'm likely going to do)
- #2
dwex Mon, 20 Oct 2008 14:44:54Been looking into this some. I have some code changes I will try when I get home.
I think the error is in the logic in Coconuts:GetStateBasedOnModifiers(). In particular, I see two problems:
- Flight form seems to be tied to the 2nd-best modifier. Which is probably correct for ground mounts, but not for flying, where instant-cast flying probably causes druids to just use flight form, in preference to flying mounts, except for vanity mount situations. This may want to be split into a separate preference for flight vs ground forms.
- Even if that were bypassed, the form check is INSIDE the conditional for Self.NextCurrentXXX Well, as a druid with epic flight form, I have no "normal" flying mounts. Hence Self.CurrentFlying/Self.NextCurrentFlying will always be nil, and the form check is never made.
Basically, this code needs a bit of restructuring to (a) do form checks independent of any 'real' mounts, and (b) give precedence to flight form over 'real' mounts.
I'll test that out tonight and post an update.
- #1
dwex Sun, 19 Oct 2008 14:57:12Still not working with 2.5.94 downloaded from WoWI today.