Well if we’re talking about the mechanics already existing?
Changing specs already exists as a mechanic.
And yeah are there affixes in TBC dungeons?
Affixes are already in the code, since it’s a legion client.
Remember, you argued earlier that dual spec was already in the legion client code… so if that’s in there, despite not being a feature that’s been used in 2-3 expansions when legion came out… the legion affixes are definitely in there. Just need to change damage values.
1 Like
I did, but similar to retail specs affixes are not a stand alone change 
They carry a lot more baggage than just switching specs.
Of course, an extra entire feature is more of a change.
But that’s not really what was asked. Nor is it a reason to not do it.
They are equally feasable and admitting one takes more development time doesn’t change that. So I’ll accept that as tacit admission on your part that yes, they could add it.
1 Like
We are talking about dual spec… Not boosts, or anything really damaging. Dual spec would only encourage people to play more… Maybe it could be a beginning for someone to try a new playstyle, or give pvp a shot to get one shot without pvp gear… Why are you against this? It does NO HARM to the game unlike boosts which have already screwed it up past redemption…Give me a break…SMH.
The argument ended here:
Blizzard can add anything they want.
Dual spec is however a feature that actually existed with the current talent system.
If dual spec currently exists with current talent system (which it doesn’t but we are using your logic pattern)
Then that means mythic+ also already exists with the current dungeon system.
It’s just adding on to what’s already there right?
And using the legion client means the coding is already there as well right? Because it exists in the legion client.
Remember I’m applying your logic pattern to this.
Yep all of these things could be enabled at will by blizzard.
But we are only talking about dual spec.
Nope, if dual spec is on the table for discussion, then so is mythic+. You can’t explain to my why mythic+ won’t work for tbc.
Yet you request I do so for dual spec. You are creating a double standard because you have an agenda. If your agenda was what’s best for the game you would explain why mythic+ was bad. Instead your trying to push the conversation to the side and ignore it.
This shows your agenda isn’t what’s best for the game, it’s what your personal preference is and you don’t care what’s best for the game.
It’s been shown that adding dual spec early robs tbcc of part of its identity, as well as robbing the future wotlkc of a good part of its identity. And you want to do it in the name of convenience. If you thought the restrictions on respecing was the issue stopping people from playing the game, you would be arguing for a far more successful system for fixing that issue than what dual spec does.
You would be asking for those restrictions to be removed or reduced to the point it wasn’t stopping people from playing other aspects if the game. Instead your asking for dual spec, a system we know won’t fix any problem, and your asking for it for the sole reason of YOU wanting it.
Never said Mythic+ wasn’t on the table.
You want it start a thread.
Pushing the topic to the side because you have an agenda that isn’t what’s best for the game. Got it.
So you support dual spec as long as we get mythic+?
- I like the Donkles solution.
- This has to be about the most confusing thread ever with two z named night elf druids going back and forth.
1 Like
Mythic + would work just fine. If it’s just more difficult versions of the Vanilla and BC dungeons I’d guess it would be easy to add. But depending on the loot tables of if it’s new dungeons it would likely take significant dev time and likely be refused for that reason. That’s why we ask for dual spec. It’s likely that can be added with very little dev time.
I didn’t go to the discussions on HvH bg’s to ask for dual spec. Those were discussions of HvH bg’s not dual spec. I’m glad that the players asking for HvH bg’s didn’t come to the dual spec threads to ask for it. Most people respect the topic and start a new thread when they want to discuss a new topic. Only a few clueless people bring up off topic posts.
-
It should only matter whether the solution addresses the use case. A popular solution that does not adequately address the use case is still a bad solution.
-
DS is only “popular” because this entire campaign is being pushed from the top-down (making the problem fit the solution) rather than encouraging debate to formulate a good solution.
I deal with stuff like this at work all the time. Somebody has an idea on how to fix an operational shortcoming, rallies a bunch of stakeholders together by pitching the merits of their specific ICT solution, then I have to un-do the work of their campaigning until people realise there is actually a better solution than has been sold to them by well-intentioned but short-sighted colleague.
Sometimes I can’t and we’re forced to begrudgingly release a sub-par enhancement that will invariably leave people disappointed. But hey, it was popular in the planning phase!
DS is popular because it was used by most players. They understand it. They know how it works and most people liked it at the time. It’s a small change and most people think you’re more likely to get a small change out of blizzard. You’re projecting your problems from your job onto the forums and I don’t think it fits with what’s happening here.
I’m fairly sure it’s the DS proposition that authenticity is no excuse for poor game design. If a change is good for the game, it should occur.
If people accepted that they want DS simply because they like it or disagree with the design philosophy of TBC, I’d completely agree with you. But people keep insisting it’s a problem. If it’s a problem then let’s treat it like one and find a solution.
Not at all, I’m just showing how bad of an argument it is for supporting dual spec that “it would work in tbc”
Sure, go ahead. Work with those who have a problem with dual spec and see if you can come up with a solution.