-
Notifications
You must be signed in to change notification settings - Fork 17
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
only ground mounts being chosen in WOTLK zones #205
Comments
I can't seem to replicate this using the current versions. Are you still having this issue? |
with the newest version of retail and version v.2.0.7-alpha1 of bestride, /click BeStride_ABRegularMount does not function at all for me rolling back to 2.0.6 is still fully nonfunctional, as well |
It does work for me. Can you open the options? |
yes, i can option the options and alter them freely. but i can't use the addon to summon mounts |
I get this, too with bestride 2.0.6 on retail 10.0.2. The problem is that the IsFlyable() function in logic.zone is looking for Cold Weather Flying (54197) when continent.mapID == 113. However IsSpellKnown(54197) returns false. Cold Weather Flying is no longer required to fly in WotLK zones in retail. If you comment out lines 163-165 in BeStride_Constants, then bestride is able to pick flying mounts in WotLK zones. (Maybe I should say Northrend zones, since, to be clear, this is on Retail, not Classic.) |
This is not a viable solution as this addon now needs to support both Retail and Classic. A check for the version of the game may be more appropriate. |
Confiming the same behaviour in version 2.09. Only noticed as I was levelling some alts. |
WoW Version
Retail (9.2.5)
Bestride Version
2.0.6
Steps to Reproduce
type /click BeStride_ABRegularMount in any WOTLK zone (personally verified in dalaran, icecrown, scholazar basin, and borean tundra) with flying mounts selected in the /br menu
Observed Behavior
only ground mounts will be summoned despite being able to fly in these zones
The text was updated successfully, but these errors were encountered: