Blue post telling you its not the same, while you still insist its the same
As usual you love to quote to blue posts that fit your narrative and ignore the ones that do not. Its perfectly possible the events OP described did not happen in vanilla while they do happen here.
Its easy to say “nobody has been able to prove it”… well yes because all the players have are super old videos that are a mashup at this point from the original game as well as various pservers and that probably will not show a scenario described like the one OP complained about.
You are flat out wrong, we’re on a modern version of the server engine which has a significantly better version of batching than what existed in vanilla. The junk we have in classic was cludged into beta very very late and has no reason to exist at all.
I’m not wrong. There has been zero legitimate evidence provided in any of these threads that batching is functionally different on Classic than it was in Vanilla.
Statements like this:
Show me that the people arguing with me here don’t know the subject well enough for me to even consider wasting more time pulling up all the old Blue posts, videos and other evidence I have proving it’s working exactly as it did in Vanilla.
Pretending that batching is “wrong” and asking Blizzard to change it based on that faulty presumption isn’t going to work. Blizzard hasn’t touched it in over a year because they KNOW it’s working properly. The ONLY way they’re going to ever consider changing it is if people appeal to their recent statement about erring on the side of fun:
The community needs to admit it was wrong and kindly ask for a reversal on the batching implementation. That’s it, that’s how you get batching removed. Not by blaming Blizzard and lying to yourself that they “got it wrong,” or anything else.
Admit batching sucks, it always sucked and there’s a reason they put so much effort into changing it.
I use to think it was gonna be really great, but it’s not really great.
The best thing we as a community can do is to come together on this thing and give up this classic batching thing in favor of what is a more practical solution that exists by default in the game server. In other words, retail’s system for handling things in order as they are executed.
This would be a blessing for literally everyone playing classic or later TBC.
I dunno, Nost used batching, as well as other popular pservers. For some reason people had no issues with it there. 1.12 does feel different than 1.13 for sure.
That bluepost was referring to Retail when it said “nowadays.” Classic was put back onto the single loop. This is why we have “vendor lag”, because all actions a unit takes on another different unit are now batched, just like they were in Vanilla.
Spells that you cast on yourself are not placed into the spell batching loop. This is why a Paladin can use Divine Favor and batch Holy Shock by casting it immediately after a heal. You’ll get two free crits instead of one; this only works when you cast the Holy Shock on another player.
The batching we have is functionally identical to what it was in Vanilla. It’s a 400ms loop that all unit on unit actions are placed into.
Except classic is still using the modern batching system which is different than vanilla batching system. All they did was change it to 400MS instead of as fast as possible.
Which is why it doesn’t function the same as it did in vanilla.
Sorry but can you read? Aside from quoting a post from 2014 (Patch 5.4.7); was that WOD(?) you again ignore what the more recent blue post added.
They literally tell you they just put spellcasts on a low priority instead of a high priority and it “best fits the game how the game actually worked in version 1.12”. Where do you read that its a single game loop again? Cause try as I might I can not find that in said blue post. Not to mention that “best fits the game how it actually worked in 1.12” does not equal “its exactly the same”. They literally state its not the same as the 1.12 batching.
Go ahead, ignore the blueposts that do not fit your narrative and then claim some non-sensical reason on why you will not respond to anything. Anyone who reads 5 of your posts knows already that you are mostly smoke and mirrors.
It’s not even worth trying to help you understand anymore.
Spell casts aren’t the only thing they put on the loop, they didn’t even say that spell casts were the only thing they put on the 400ms loop.
Vendor interactions are batched. Try to sell things to a vendor on Classic and then do so on Retail. This is evidence enough to show you that every unit on a different unit action is batched just like they were in Vanilla. The batching we have is identical to Vanilla batching.
A blue post that says, and directly contradicts the blue post i linked, saying its the same would help. But it is not. Because this is 1.13 and it is not 1.12. The game is working differently now and they added a hatchet job of batching to it-
You can keep bringing your vendor interaction argument as long as you want does not change the fact that what the blue post says completely disagrees with your little fantasy story. I still wanna see the “its a single game loop” blue post quote btw.
“we’re only moving spell casts to a low-priority loop”
but it doesn’t. They were specifically talking about spell casts because of the interactions they mentioned in that same post. The simple fact that vendor interactions are batched on Classic is proof enough that they extended the batching beyond spells.
The batching we have is functionally identical to what was in Vanilla. You, nor anyone else has provided any legitimate evidence to prove otherwise.
you do not have any shred of evidence that it works correctly either. The only thing we do have is the blue posts and they say themselves its not the same. It just fits best compared to the original one.
