I don’t get for what. And Please don’t say for when you’re going afk.
They also prove that they do budge on a lot. There’s no basis to “highly doubt” that they won’t do anything about this. Considering that their current swapping solution is incredibly clunky, I’d be surprised if they didn’t iterate on it.
I’d be more than okay with that solution, but given it more thought and I think it would genuinely be more technically challenging than blending the two styles together. It sounds simple but on second though, it would be a per player, per mount basis, with hundreds of mounts per player, which is a lot of information that would need to be stored somewhere. The question would also be if it would be feasible to have it per character, or if per account would suffice, because a per account solution wouldn’t solve mounts that are faction or class-specific.
Considering that they took 2 years to increase the number of something as simple as talent loadouts to more than 10 per character, I find it difficult to imagine how they’d deal with this.
If you don’t like the idea that’s fine but I still have yet to see why it would be bad for the game overall, which you’re trying to imply. The only difference would be that instead of landing and summoning an entirely different mount, you’d just swap on the go, making flying literally even more dynamic.
Blizzard is not “in the end”, they’re at the beginning of everything that’s added. What in the end decides what sticks is the players, and flying is probably the best example you could have given to unintentionally prove this. Hence what Blizzard thinks about this is hardly relevant in the end.
That part I never did disagree with. Not sure in which forum I did write about it, but I still have a little hope that we might see something here with the “system updates” which will come in 11.0.5, but it’s more likely we won’t see a change before 11.1 or 11.2.
I can tell you, from a developers perspective, also handling bigger databases, it’s actually the way easier and better solution.
If you look at data usage: You already do save the default per player and for the mounts you’d just put it in a second table and only put a row for the mounts which the player actually does change for the specific char.
Think about it. Mounts of inactive accounts (or chars) don’t bloat up the table, since nobody changes mount-settings there and for players like me with 600+ mounts, let’s face it, we only change a hand full of mounts, if at all. The rest will be standard.
Me and a few others actually did think this one through weeks ago. 
For the flight form you just add a glyph (or 2…one for each mode), that system is already in place.
And from the actual implementation standpoint: It would be a lot less work, a lot less code to change with a lot less possibilities for bugs than your suggestion.
Would you believe me, that in the beta threads about this in the US forums there were a lot of people who did actually did whish for blizz to completely remove static flight altogether? (not me!)
I still think it would keep more people happy (also me) if we keep both flight modes separated and just fix the current problems, by adding a per mount choice.
And actually I would for sure prefer a per mount choice from takeoff to landing. I don’t want to start in static flight mode if I want dynamic flight and I don’t want to start like in dynamic flight mode if I chose a mount I wanna use in static flight mode.
They’re in the end and in the beginning. We’re the feedback in between. And for them to combine both, you’ll need a very strong voice of a lot of people. And while there are a lot who want a change, I doubt you’ll get that kind of outcry, you need to get your change instead of a change.
Actually, it’s not. As I did say, they did want to change it, if everything works fine. That does not only include the technical standpoint, but also the users. There was an outcry to that or to not being able to use static flight in DF…I think it was the latter. So, the test did fail. As you see, keeping static flight was already planned as a backup plan from the beginning.
It is indeed
Never understood why it couldn’t retain its ability and just be unaffected by mount equipment
2 Likes
Also didn’t like that change at all…it was so unnecessary…using “waterwalking” on all my mounts since…but I would still prefer putting different mount equipment on my mounts for my priest, etc and still use waterwalkling with my waterstriders.
That’s still pretty much guaranteed to bloat up over time as people tag more and more of their mounts adding up to hundreds of rows per player, unless they limit the amount of mounts you can assign a flight style to.
What you’re describing is a no-brainer in an isolated scenario, but the truth is we don’t know how their back-end works so it may or may not be as simple as that. Considering this solution would have worked exactly the same for talent loudouts, but those were limited to just 10 per character, there’s good reason to assume it’s probably not as simple.
I’m not saying it wouldn’t likely take more time to develop as it’s also a completely different approach requiring changes to the actual flying system rather than just adding a table in a database. Again, we can’t know how much work it would be to change flight style without dismounting, just as we don’t know how much the bloat from setting the style per mount would affect the game’s performance down the line.
That said, I’d still be okay with a per mount flight style system.
No reason not to. Threads about flying “breaking immersion” or whatever pop up somewhat regularly everywhere, but I seriously doubt that it would be a common sentiment if you polled the playerbase.
I was trying to avoid stating the obvious, but yes, Blizzard ultimately holds the power to do whatever they want. It’s just not in anyone’s interest to use what they want as an argument for what should be, unless it happens to align with what you yourself think, but in that case it would just be a case of good old confirmation bias.
I’m really confused what you’re trying to say here. Yes, Blizzard wanted to get rid of something, players didn’t like that, so it was kept. That’s exactly what I’m saying. What Blizzard’s original vision or intention was matters little if players don’t agree with it, so saying that in the end it’s up to Blizzard says nothing, unless you expect them to shoot themselves in the foot just to stick to their guns.
Not really. Tenths, but for sure not hundreds and on average over the active playerbase it will be probably even in the lower 1 digit numbers.
That’s for sure. We did extra pick something that should give you an average idea. Can be (a bit) worse or it could be even easier. And if I’m right about how they nowadays organize data, it would be even easier and more storage saving to do than a table in an RDBMS.
Oh and talent loadouts take considerably more space, than what I do suggest for the mounts. Also I’m pretty sure talent loadouts are saved in a versioned manner. Same like the export strings are versioned.
I would go as far as to guarantee you, that your approach would be considerably more work and error-prone than a simple override. I’d even go and say it’s safe to assume that way more code could be reused this way.
But it is, if you have an alternative, that caters to a broader playerbase, which is: do not combine them. And they’re not the only ones who don’t want it to be combined. I’d count me into the “don’t combine it” corner as well. I simply don’t like the idea of it and think it would inconvenience me and I’m sure there are more who think same.
Or if you have alternatives, that would fit as well and would be easier to “sell” to blizzard as a good idea.
What?
Look 2 situations:
Scenario 1: Blizz plans to exchange a system, but is not sure if it works out technically and if they can “sell” it to the playerbase as a good thing. Blizzard tries it out in a new expansion with the new system in the expansion content and the old system in the rest of Azeroth, with “if it doesn’t work out, we just go back to keep the old system next to the new one, both have their own benefits and people will use both”. So it is a test-run with a fallback in place. That is nearly A / B testing.
Scenario 2: Blizz is implementing something to stay. No test-run if people accept it or something like it, no fallback.
You see the difference? If the players in scenario 1 complain and Blizz goes to the fallback solution (like with dragonriding vs BC flying), it is not a proof at all that if in scenario 2 (some) players are unhappy, that something similar happens. And if the past did teach us anything than that we need a huge outcry for letting changes go our way, not only some people complain a bit about s small part of it.
The outcry about the change in flying was bigger in the beta than now and the outcry about the warbank prices in beta was even bigger (in my eyes) unless you count in the thread with the problems druids have to deal with because of the change, then it might have been slightly bigger than for the warbank cost.
You know what was even bigger and blizz didn’t paddle back? The outcry from tanks about the big tank nerf and blizz still continues down that road.
Do I think they will do something about the current situation? Yes…at least I do sincerely hope so. Do I think they will implement a whole new mushed together flight mode and replace both of them with it? I doubt it, especially if you consider the past.
Keep them two separate.
Idk how many times i mount off just to kill few mobs to recharge a vigor.
You have no idea how the system even works.
Lower 1 digits numbers on average is seriously lowballing it.
A thing I also just realized while typing this out is that with the ability to assign a particular style to each mount, people would most definitely start asking for the ability to summon a random mount of either style, just like we have the ability to summon a random mount now, which would be difficult for Blizzard to ignore long term. And with that ability the number of assigned mounts would go up considerably.
You’re right. For some reason I thought the strings were much shorter than they are.
I am still not disputing this, I just don’t think that something taking a lot of work should disqualify it from consideration. The whole game is packed with features that are aren’t simple to implement.
I was talking about flying as a concept, not my idea for combining the two styles.
Yes, but you’re now talking about something entirely different than what I criticized you for which sparked this part of the argument. What I was calling you out on is trying to use Blizzard’s vision to justify what they’re doing.
You were going on about the strengths and weaknesses of each style and how it needs to be balanced, which you claimed is what Blizzard’s idea is. I say that’s irrelevant and balance shouldn’t be a serious consideration when it comes to something like mounts. I’m calling out both Blizzard and you for even taking that into consideration instead of how fun, satisfying and convenient flying is or should be.
I highly doubt it’s lowballing it. I’m talking about the average over all chars. And even if it wouldn’t be in the lower 1 digit numbers, I’m still sure it would be in the 1 digits.
- Not every char is played actively or at all
- Not every player will change a default
- Not every player who does change a default will change it for every character
- Most of the players will most likely change only a few to one flight mode
Don’t forget, if you i.e. most of the time use dynamic flight, you don’t need to set any of them to dynamic flight. You would just set a few to static flight, so you can use them for that. That is the beauty of it, it saves data and is more convenient for the player.
To be frank, I wouldn’t wonder if they do ignore it. Look in what bugged state the current function is already. But even if they will change it to 2ish buttons long term, same rule like before applies, you don’t need to do a lot of settings, if you use the default as well.
I wouldn’t worry about a lot of settings here.
I don’t dispute that, but considering there is an easier alternative and there are even people against that solution and considering there stand on static flight, I don’t think blizz will consider it (much).
And to be honest I still don’t see the appeal in your proposal over 2 separate flight modes with a solution for the current problem aka a setting for each mount. But yeah, every idea that is not just easily identifiable as trash should be considered and even I wouldn’t consider your idea as trash.
I think you misunderstood some of the things I did write or maybe I didn’t communicate them good enough. English is just a second language for me after all. We exclusively speak German in daily live in Germany. Things happen.
Blizz would in my opinion based on everything I heard and read over the last years about Dragonriding and the old BC flying, never put them together, because they don’t like the idea of the old style flight anymore. I think everybody knows they’re unhappy with it since years. Don’t forget they did already plan to completely remove it during or after WoD. That is also one of the reasons, why they did want to replace it with the more engaging dragonriding later in DF.
In both cases they did take the fallback solution “keep static flight”. That is also the reason why they lock static flight again behind the pathfinder achievement in TWW. Even though it is easier and faster to get this time and from the start in the game.
I still highly doubt they will suddenly change their mind and say “no problem, we combine both flight-modes into one” and thus remove all downsides of both flightmodes.
Instead, I’m sure they will keep the flight modes separated. And that is what they do balance to some extend, in a way that there is always some incentive (the speed) to use dynamic flight. And that balance is, why they would for sure also never raise the speed of static flight too high.
I hope this time I did succeed to communicate my points better.
To be hones, I quite like my flight modes separated and for me it is more fun, convenient and satisfying that way. And while I’d love them to add per mount settings, like I wrote quite a lot of times. Even in the current situation it feels more satisfying and fun to me than the combined mode looks maybe not more convenient, but also not less.
Nearly forgot this one…
They were btw. not talking about flying should be removed, they were arguing static flight should be removed. For several reasons. I don’t agree with them, but at least when you keep the flight modes separated you accommodate them to some degree. If you combine them, there will be an outcry from that direction.
I would argue inactive characters don’t play a role at all as I doubt Blizzard would struggle with the storage. What is important is what’s loaded while playing. As for how players would assign their mounts, sure there’d be cases of people just setting one mount to each style and never changing it again, but a considerable amount of people would over time accumulate more, be it because they get bored of the current mounts and assign new ones, or because they just got a new mount and give it a flight style… in a few months a ton of people would be way above single digits.
Anyway, I do concede that this would probably not cause issues as it would take quite a few assigned mounts to take as much memory as a single talent loadout.
Oh don’t get me wrong, I had zero expectation that Blizzard would do this. I was just speculating about what I’d like to see and defending my opinion.
I think a combination of both might be the best, although I do not see that happening as much as I’d love to. So setting a default flight style per mount but also being able to swap mid air as I described early in this thread.
I just find the idea of being in static flight and entering skyriding mode with a smooth animation and momentum boost, as well as transitioning back into static mode with an aerial halt into hover, quite exciting. Complicated to implement for sure but I’d love the ability to fly around like that, and simply don’t see the downside to it.
The question is, what they do keep in memory anyways and how. In theory the state of the setting could be expressed by 2 booleans “is overridden” and “flightmode” (since we only have 2 of them). Which in theory could be expressed in 2 bits. Mounts might expressed by an integer which in turn, with the size of 32 bit and 64 bit integers would be big enough to also house the settings. But to be honest, even I doubt that is how they keep it in memory for…well…so many reasons. 
I still think you overestimate the amount of players who would actually a) use the settings, b) use it on more than one mount and c) switch it up a lot over time.
Me for myself would probably not even change the default of any mount and just use the otterworldly ottuk which only has static flight anyways and for druids, I might change the flight form…maybe.
And maybe after a few years, I might change to a different one. Most of the time I fly dynamic flight anyways, which would be my default setting
Oh, OK…I guess I don’t because you said so
I know exactly how it works and this would be a “change to” how it works
They don’t lose viger while hovering. They just don’t regenerate any.
Also, they don’t hover when motionless, and they slowly fall.
So no, I know you don’t have any idea what you’re talking about. I agree about changing the cast time for switching it as 5s is too long, but changing the current dynamic flight system just ain’t it.
I know that and I guess so does everyone else.
You might have missed my initial point to the post but I don’t want to argue about it so let’s move on 
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.