Please find a way to reintroduce the spell batching system that was changed/removed in 2014

They literally said in the blizzcon panel that although debuff limits were a technical limitation, that they were re implementing it.

Also, the default backpack had been a technical limitation for years, and the reasoning for that was the amount of spaghetti code that the backpack was covered by, so they were unable to change the backpack limit without changing a LOT of code.

2 Likes

You’re clueless.

2 Likes

Didn’t read your text wall but they should not add ANYTHING that was not there in vanilla ! That’s the entire point!!! It’s just mind boggling how you peeps can’t understand that simple concept

2 Likes

This post is about requesting a system that was there in vanilla. Spell batching was a technical limitation during vanilla, as was debuff slots, the backpack slot limit, and many other things. I am requesting a system that was part of the game from vanilla until the end of MoP.

I’m glad that you also want to be a part of an authentic vanilla experience that the devs have committed themselves to, but please read before commenting in contrary to something your comment appears to be in support of.

2 Likes

Clearly…

@OP, I agree. I never knew what spell batching was but looking at the explanations, I feel it would be a great disservice to NOT have it in Classic™. To those opposed, just because it was used because of limitations does not make it a bug or exploit. It was put into the game intentionally and should be there for Classic™.

5 Likes

To say that it was an exploit would be to say that 16 debuff slots is an exploit. This was very well put, and I thank you for your contribution.

I would also like to add for people that didn’t read my initial post; this was a feature until the launch of warlords of draenor.

4 Likes

Whether you think it was random or skill based is irrelevant.

It was in Vanilla. It contributed relatively significantly toward how PvP felt.

Thanks to the OP for bringing it up, its a point that hasnt had much discussion, but is something I think was iconic to the experience.

I don’t know the amount of effort necessary to re-implement in the modern client, but this is an issue that definitely deserves consideration.

5 Likes

Argument is moot…there will be no batching as they’ve decided to work backwards from the current game instead of the old version of vanilla they had…

1 Like

They don’t even have to work that far back, this mechanic was removed in 2014 with the launch of warlords of draenor.

3 Likes

It’s not a mechanic that was removed, it’s server behavior that was fixed to behave consistently and better.

1 Like

It was consistent at 0.4 seconds/tick. That is not inconsistent. The gameplay that resulted from the “upgrade” was also worse. There is a reason wow pvp has hit it’s peak a very long time ago.

Just because something works well on paper, does not mean it works well in practice. You can look at many philosophies/practices throughout history that prove this supposition.

4 Likes

It wasn’t consistent though, that tick was a server side tick not a tick based on when you cast your spell. The blue actually explained quite well how that resulted in anywhere from almost none to up to 400MS lag, entirely randomly depending on when you happened to fall into the queue.

Just because something works well on paper, does not mean it works well in practice. You can look at many philosophies/practices throughout history that prove this supposition.

Right, the batching system sounded okay on paper but in practice it was pretty bad, hence why it was fixed.

1 Like

You still, after so many forum threads and posts contradicting you, do not understand this sytem.

This is what we call a propositional fallacy.

2 Likes

It’s not my fault you can’t understand how the system worked even after a blue very clearly explained it and explained exactly why it lead to such erratic behavior.

1 Like

I’m going to break this down for you in terms you can understand;

This sytem was in vanilla, and as such should be in classic.

Just because you cannot understand the system does not mean it didn’t work and was an rng system that could not benefit anybody.

Just because you do not possess the mechanical or psychological skill required to correctly make use of this system, despite it being a technical limitation of it’s time, does not mean that it has no merit in the recreation in the game that we all love.

Please stop posting your small minded, contrarian, misinformed opinions.

7 Likes

Server pop caps (in terms of players online) was actually limited by design and not by tech.

1 Like

This is correct. What I was referring to about the information given at blizzcon (Press Q&A i think?) is that while this was not, and is still not, a techincal limitation, it is flexible. That being, that the server pop, or other parameters of the server are able to be changed. For example, the processing rate of the server.

A server may be able to be edited so that the batch processing of player input could be at 0.4 seconds, thus recreating the combat experience of classic WoW.

As a side note, it was very interesting to hear from an interview from Mark Kern, that smaller realm pops were actually less financially feasible for them at the time, but they stuck with it anyway due to a design philosophy pushed by (insert dev name here, I can’t remember his name).

1 Like

Nah. Not required.

2 Likes

Please refer to the final section of the dev watercooler titled “looking ahead”.

“Additional improvements will include modern anti-cheat/botting detection, customer service and Battle…net integration, and similar conveniences that do not affect the core gameplay experience.”

This system impacts the core gameplay experience.

3 Likes

It impacts PvP, and it’s inclusion would make PvP players (and Classic players on this forum in general) happy, yes?