#nochanges You Think You Did, but You Didn't

It’s no changes… except the ones that come with phase 2 and phase 3 and phase 4 and phase 5 and phase 6 and if there’s expansions the changes from BC and the changes from wrath. But other than that NO CHANGES. rotflmao

It has no place in Classic, as it never existed in the original version.

#Nochanges.

1 Like

Well, you are right. You did attack me. But I’ve talked about other things and not just the Slippery Slope, which is still true, no matter how many times you spam the wiki page link and attack me, personally. Nothing else has come from you other than that.

Again, Blizz’s changes does not equal my acceptance of them.

Spamming a Wikipedia post and then spending the next hour calling someone an idiot, a narcissist, and a Machiavellian does not particularly constitute “constructive discussion”. Neither does calling you a smug, self-righteous bully and telling you to get off your high horse, to be fair - but in this case, it has the virtue of being true.

Couldn’t make that up if I tried…

^ See that post.

Slippery Slope is an informal fallacy, surely if you are in to philosophy as much as you are acting, you will know what that is. So stop acting like it’s a formal one.

Rather than continuing to repeat rhetoric about him being fallacious, start arguing the reasoning as to why he is wrong instead. It shouldn’t be hard if you are good as you act, since he isn’t doing a very good job.

The argument itself is not based on nothing, or merely paranoia, but on recognizing patterns within Blizzard, and seeing the end result of those patterns. Many of the “no change” crowd probably would not mind some minor changes here and there, but they prefer not having any changes for an assured product that is (as close as possible according to Blizzard), over advocating for minor changes and risk others inevitably asking for major ones, using the argument “Well you changed X already!” which would be a valid argument at that point. The expression “give them an inch and they will take a mile.” comes to mind, which has been observed throughout history, and not merely fallacious speculation.

Personally I’ll take millennia of historical examples, and common observation, over an article made by random people online, on a site that’s own co-founder has said is unreliable.

4 Likes

Would it make you feel any better if I said he was combining a false dichotomy with a continuum fallacy?

I do agree with you, but I’m not going to stoop to their level of insults, either.

OK, please state why it’s a fallacy, in your own words, without the help of wiki and just saying, “it’s a falllcy!” Followed by a montage of insults.

You have a far greater patience with his lot than I do, to be fair. I’m actually wondering how I got here in the first place, but c’est la vie…

1 Like

I mean, if I ascribed to the #nochanges false dichotomy, I’d get irate when someone pointed it out in the manner that I did. I understand. I can’t say I sympathize with that level of delusion, but I understand.

Past experiences shows, along with history that you give people an inch, they request a mile. Look at the four “suggestions” of changes in my OP. Can you, honestly, tell me, that the implementation of all four of those “changes”, does not take away from the integrity of Classic?

Exactly, we’ve all already been through this before. Why would anyone want to risk losing this second chance by repeating history?

I doubt we’ll get a third opportunity.

#Nochanges.

2 Likes

People love to say “There have been changes” and think that is reason enough for their own wants on what they want changed. The reality is those changes you keep referencing have 2 reasons for those very changes.

  1. The change was needed to function in Blizzard infrastructure at present which was not there in 2005.

  2. The change occurred because Classic had a different out come than in Blizzard’s Vanilla reference client. Any end result that happens in the Vanilla reference client should mirror that in Classic’s client.

They then try to piggy back on any changes Blizzard make as a “Oh, they made this change so it’s meaningless to argue no changes”. These people have an agenda to get their small and insignificant change into Classic solely because they just want it. They hate the fact addons do the exact same thing and want it to be similar to what is on retail to make their Classic playtime easier or more pleasing to them. Do not be fooled into thinking #nochanges is irrelevant. Supporting any WoW community changes opens up the flood gates to other people wanting those very changes that will make Classic more comparable with retail. Blizzard have only made changes that either had to be done for Classic to function correctly or the change was relevant to Vanilla and how it functions.

Stop trying to skew the changes so far as counter productive to the #nochanges community.

3 Likes

BFA was 15 years of changes, yet you suggest that minor QoL changes would implement take the game to retail. That’s a false equivalency, first of all. You also engage in a false dichotomy by suggesting the game can only be Classic or Retail, while in reality there are numerous states this game has existed in and a nearly infinite number more it could exist in. I’d also suggest that you’re splitting (Classic is all good and Retail is all bad). That’s 3 separate logical disconnects in one argument.

The #nochanges community is a joke. Not all changes that have been made are infrastructure changes.

Players can’t even agree if features introduced in TBC was the beginning of the end.

It’s not worth the risk, we’re here to play Classic WoW, not your ideal version of WoW.

#Nochanges.

1 Like

yeah and like i said they have been changes that reflect vanilla reference client. The #nochanges community is to stop people like you from changing vanilla as its core.

3 Likes

Players can’t even agree that there was an end. What metric are we going by, player count? It peaked in WoTLK, so if that’s your metric, I’d say it’s patently false that TBC was the beginning of the end.

You don’t deserve any other response than #Nochanges.