By and large, players “dealt” with respec fees by choosing to not respec and choosing not to participate in other aspects of the game (battlegrounds, arena, trying new specs and roles). The developers realized that was bad game design. It’s one of the few QoL changes that there aren’t strong arguments against, imo.
I don’t have profession alts. I have 1 main and play maybe 2 hours a day (at most) on days a work. I do the cooking and fishing dailies (and summer Sustiva dailies while they are here) and a few quests I saved to do at 70 (when more dailies co.e out this won’t matter as much). My professions are engineer mining. And I do the daily dungeon / heroic about 4 times a week. I went from about 100g after hitting 70 (and buying normal flying) to being at 800g now with epic flying after about a month of play and with donating a lot to my guild.
I don’t play a lot, I’m just efficient when I do. It’s not a 400g/hrs efficiency, but it’s at least 100+g an hour.
Uhm no, the baby doesn’t have to be thrown out with the bath water. Just because FvF was forcefully added doesn’t mean we are “for” it, I’m sure most of us who are against dual spec were against FvF all the same.
You say on an Alliance toon. Idk if you saw the Horde side of things for queues, but I’d gladly fight premades and get rolled consistently than take a dub after an actual absurd amount of time waiting.
FvF imo is a health change for the game. It may seem only QOL for the Alliance who didn’t deal with spending 6 hours a day on the game, with 4 of those hours in queue, and and hour in BGs, and another hour not in queue or bgs cause you don’t have the time to wait for another 2 hours for bgs.
It got “better” in TBC, going down to an hour, but that’s still absurd.
memes and jokes aside, having a core issue persist for years that hinders the players ability to play the game based off of things that Blizzard can easily control and only exist due to arbitrary limitations of the time is not a positive to have for your game that is bleeding players daily.
You’re right, I went Undead because I have played Horde my entire life, since I was 10 or 11, and I went Undead because Blood Elf was not in classic, and out of the 3 rogue races, I don’t like buff pickle or skinny pickle.
How are we supposed to know that the Alliance would refuse to queue in so many droves that the Horde would end up being so massively overpopulated on the pvp side? You say it like we can predict what hundreds of thousands of players will do.
Not only was this the case in Classic Vanilla (the queues), so you could see it a mile away coming in TBCC with the inclusion of the Blood Elf race, but it is well known and immensely propagated that TBC servers are vastly horde overpopulated.
This problem is not unique to TBCC, nor is it the first time this issue has manifested itself.
TBC private servers have been dealing with this for as long as they have existed, and I don’t think you have any excuse for not simply googling what faction balance would look like in a modern TBC setting. The only excuse you have is ignorance, and that’s on you.
Ah yes, the game that had poor optimization and could only hold 20% of the servers population that we had in the variation of vanilla.
We are now basing modern coding to dated coding and calling it equal.
Yes, because by the time TBCC came around, we had already been dealing with queue times being an hour for WSG and AB and on average, 2 hours for AV.
It actually got better with TBCC, where WSG and AB dropped to about 45 minutes and AV dropped to an hour on average.
Parading facts without evidence I will say that Horde are more popular than Alliance, but even if we said Horde was 70% and Alliance 30%, which is isn’t as it’s more, way more balanced than that, the pvp queue is not based on total population but instead is based on players in queue. The other half of the problem of Horde having too many pvpers is added to by the fact that Alliance doesn’t have enough people in queue, and the faction imbalance is not that great to have an affect on it itself, the pvp imbalance is based solely on the PVP POPULATION which is actually massively imbalanced. If it wasn’t, Horde wouldn’t have long queues, and Alliance wouldn’t have instant queues. You’d see the queue times be closer together, instead of instant and hour.
Because they have always had correct and relevant information.
Because faction imbalance equals pvp faction imbalance, despite that the faction imbalance isn’t that great while the pvp faction imbalance is massive. It’s almost like it’s two different populations.
I said “Classic Vanilla”. As in, the game we all just played for ~2 years. Not the 2005 version.
Um, we aren’t talking about game mechanics or coding here. We’re talking about player behavior. Whether or not the private servers are mechanically accurate is completely irrelevant to the observation of what players have done and continue to do in regards to splitting the factions very unanimously in favor of horde in TBC environments.
All you’re giving me now is excuses. Excuses for being ignorant. An impressive lack of foresight, to say the least.
Choices have consequences. That includes your faction choice. Specs are no different. Choices should have consequences.
Blizzard flipped the table on the faction choice consequence. It doesn’t mean I’m not wholly against it, and it also doesn’t mean I automatically become “for” dual spec being added simply because they pooped the bed on FvF.
Thankfully, dual spec is not in the game, and we can all hope it stays that way.
My bad, I read it and it registered in my mind og vanilla, and not classic itself. That said, while there was ideas of what could or couldn’t be as far as population goes, there was no “we know this will happen with what players choose” till it happened, as the only previous information is retail stats, pservers, and vanilla itself, with two latter options being unreliable. Retail itself, while it has it’s own population, the two games are so vastly different that we can only infer and predict how players would choose their faction, not have an absolute “we know” on the issue.
You mean the pservers that would have cross faction players because they didn’t have enough players? I know we aren’t talking mechanics, but the metrics are still scuffed because, and I don’t have data on this but can only infer, the majority of players for TBCC did not play, or did not play for any extended period of time on private servers. I tried private servers, it was a horrendous experience.
And then the mechanics of those pservers also affect the players, as some players wanted a recreation, while others went to say, Ascension, which is only wow in name and name alone.
So using pservers as a basis is inherently scuffed.
No, I’m presenting an argument that how we could have predicted a massive pvp population imbalance is unrealistic. While we can infer a Horde population bias, the overall population is not representative of the pvp population, which is the population in question. I’m sorry that you only view it as excuses because pushes glasses up farther up nose “achkutually you could have researched private servers to predict a pvp population imbalance lol 4head sucks to suck that you pay money and aren’t allowed to play the game” is the only thing on your mind.
Whatever though, I can pvp now, and you can seethe that I can finally play a game designed to be played.
Player behavior is irrelevant to the accuracy of the coding of the server.
All tbc privates were vastly horde overpopulated for the same reason TBCC is, unless you want to argue there’s a different reason, what exactly is your point?
Where is your objective analytics. We have ironforge to show player logins, and it’s… alright for seeing population, which even if we went off of that, its 46% to 54%. That’s vast? 8% difference is vast?
You’re just seething that Horde can finally play the other half of the game.
Core problem: Half the playerbase can’t play half the game.
Causation of problem: Alliance don’t queue pvp.
Solution: Let Horde fight themselves in BGs.