Dual spec has no down sides

You say that but your side of the argument has been indulging in the sunk cost fallacy ad nauseum.

On the one hand a core argument the pro camp is using is that because we’ve already had changes there is no point holding back on further changes to preserve TBC’s identity. May as well go all the way and accept that TBC Classic no longer resembles TBC.

Then you argue that those of us saying that you won’t stop asking for changes if you get Dual spec are engaging in a slippery slope argument.

Let me point out why we aren’t arguing for a fallacious slippery slope:

  1. By your own admission you claim there’s no grounds to oppose further popular change - TBC Classic doesn’t resemble TBC anymore anyway (according to your side’s proponents).

  2. We are arguing that dual spec won’t solve the problems you claim it will. We are therefore predicting that other “solutions” will be proposed. This is not a slippery slope, this is presenting a clear cause for further change requests. If the cause of this request is not resolved by it then it is reasonable to expect that further attempts to resolve it will be sought.

The Slippery slope is a fallacy because it proposes a ‘slide’ without proposing a cause beyond the initial change. But we’re suggesting that the proposed solution won’t resolve the cause (the problem) and so further change will be sought.

2 Likes

Right and the problem is dual spec doesn’t actually cause any of the crazy things people are claiming. Hence why it’s just blatant fear mongering.

Now sure if you are claiming you don’t like dual spec just because it wasn’t in TBC originally, that’s an honest and true opinion. Trying to lie and pretend it causes some massive harm to the game on the other hand is just false.

Wait, is he now saying slippery slope is a type of argument in support of Dual Spec now?

I can’t even follow these people anymore.

Please watch your language. Children use this forum.

No he said dual spec had something to do with sunk cost? Not sure how that works either.

You seem to have an issue following much of anything that goes beyond 3rd grade, rudimentary logic, that’s on display for everyone to observe.

1 Like

They seem to be throwing out these words because they’re part of a colloquial lexicon. Inigo Montoya has a few words to say about that.

:crazy_face:

Yes, exactly. Google the sunk cost fallacy.

Don’t get drawn to that posters level btw, you’re better than that. People like him get blocked.

“I can’t explain things that I don’t understand so I’m going to tell you to Google it.”

Yes and sunk cost has nothing to do with why people want dual spec.

Pointing out that #nochanges is no longer a valid argument against dual spec is by no means using that solely as a reason for dual spec.

But it’s buzzword he probably heard some guy on YouTube use, so it’s relevant to this topic…somehow!

Is not the argument we’re using though.

The argument I’ve used is that some changes are fine except where they run directly counter to the design goals and intentions of the original game. There should be some effort to preserve the identity of TBC. That’s not a #nochanges position.

All of the changes so far can be argued on the basis of addressing unintended consequences of a game design choice. Dual spec, however, differs in that it addresses and intentional consequence of a design choice.

1 Like

That sounds like #nochanges with extra steps. And also far more subjective as what you consider the identity of TBC might be very different.

Personally all I see dual spec as is a better way to do something already in game(something that is technically already immersion breaking), not some fundamentally different way of playing.

Otherwise known as #somechanges

You’re missing the “some” in the #somechanges concept.

1 Like

As I’ve stated before, you’re using logical shortcuts to basically reduce every single argument down to #nochanges, when it’s not that simple.

It benefits your argument, no doubt, but it fails to actually meet us in the middle where the discussion is.

1 Like

People have tried to discuss a middle ground, like requiring being in a city and adding a cooldown.

No, there’s no middle-ground for implementation, because we plain don’t want it in the game, you can’t middle-ground that. Don’t be mistaken.

I’m talking about properly comprehending our actual argument instead of constantly repeating, ad-nauseam, back to us “All you have is #nochanges”…when that’s not all we’ve had.

I have a feeling you feel compelled, right now, to ask “So then what else other than #nochanges is there?”.

I really bet you’re feeling that right now.

1 Like

I’ve written loads on why one change is okay and this one is not.

It comes down to whether the issue being addressed by the change was an intended outcome of a design choice or whether it was an unintended outcome of a design choice.

You are trying to solve an intended outcome of a design choice with dual spec, so the “bug” you’re trying to fix is actually a feature and not a bug. There’s no middle ground on that as the problem you’re trying to fix isn’t a problem and doesn’t need fixing.

World buffs were being used in unintended ways, and you can argue that for all of the current changes. But you can’t argue that for respeccing.

1 Like

A nice quote from Terry Goodkind applying very much to our dual spec fans:

Wizard’s First Rule: people are stupid. People are stupid; given proper motivation, almost anyone will believe almost anything. Because people are stupid, they will believe a lie because they want to believe it’s true, or because they are afraid it might be true.

They are living in their own dream world where they think dual spec would solve all their home made problems and would have no impact on the game at all. And instead of waking up, they continue to dig their hole deeper.