I want it because it was part of vanilla.
I want it to help fully authenticate the game as it was. I do not however believe like others here that it was such a major part of the gameplay.
you still want it though? i mean, i have already seen two people admit that the only reason they want it recreated is to get an unfair advantage.
and blizzard has already made clear that anything that can be used as an exploit, is NOT getting put in the game.
Could you please clarify to me where Blizzard stated that it was not an intended mechanism?
2 Likes
you actually want people to believe that it was an intended game design? lol
not a service or hardware limitation?
no.
It was a mechanism. Not a flaw. Unless I am mistaken.
2 Likes
Soo… no one in the history of anything has hit each other at the same time with anything…
Yeah what definition is that? Because I have never heard Blizzard state ever that it wasn’t an intended design decision. You can all it a hardware limitation all you want. You know what else was a hardware limitation. The debuff limit. Why are they recreating that?
3 Likes
how is a warrior one shotting a mage from 5 yards away, completely out of range- part of game design? lol
1 Like
does not equal a flaw.
To argue against hardware limitations is to ask for new models and completely new graphics because. “back then we were limited”
1 Like
now your trolling. get outta here.
AKA, you have no answer and therefore saying I am trolling is the easiest way to just dismiss my argument without having to try to come up with an answer.
6 Likes
You realize that the debuff limit was an actual limitation right?
Them re-adding it is coinciding with the concept of maintaining certain limitations that helped to keep it vanilla.
4 Likes
yep. its because i have no answer, even though that was explained LONG ago- by Ion himself. but lets pretend you arent trolling and have a legitimate point.
things that can be exploited> vanilla or not> NOT being put in classic.
it doesnt take a 5 year old to understand that concept.
That doesn’t mean it should be recreated, asking for batching just because that’s how things used to work is the same as asking for random server outages.
1 Like
Are you guys already giving up that it is not a flaw that is to be exploited? That was your primary stance to point to it as a form of cheating to align it with wall jumping.
In the realm of it being a computer limitation that affected the gameplay back then it then aligns with other limitations. This then makes it a toss up that completely relies on Blizzard. To argue from here on is to argue a pointless battle.
1 Like
You know the hilarious part of your post. Is you skipped over where he talks about the debuff limit and starts talking about mail.
Here watch the part where he calls the debuff limit a “technical limitation”
3 Likes
you never had a point to start with. arguing for ANYTHING that can be exploited, no matter if it was in vanilla or not- is never going to happen.
giving an unfair advantage, is cheating. that is a fact. it is no different than wall jumping. it doesnt matter how long it took them to fix it. the fact remains that it WAS fixed.
i didnt skip anywhere. that just happened to be where i left off when i was personally watching it. if finding the timeline you need, is to hard for you- then act like the video isnt there.
“We don’t want to mess with 1.12 data, we do not want to mess with balance”
Effectively altering spell batching effects balance.
/argument.
7 Likes
Not really it just makes spells and actually quite a lot of other stuff work consistently instead of randomly doing things that shouldn’t happen.
2 Likes
i dont think that word means, what you think it means. lol
fixing unfair advantage, somehow effects balance lol bad players are now demanding for unfair advantages in the name of balance.