https: //wowwiki . fandom. com/wiki/Sit
Sitting to get crit activating on crit effects was an oversight in development, was eventually patched so that the forced crits from sitting didn’t activate on crit effects while sitting. This is the bug associated with private servers, they never added a check on on crit effects to see if the player was sitting.
The bug we’re discussing is tricking spell batching into the actions – Attack sitting player, and stand up – being put in the same batch. This makes the attack a guaranteed crit because it was batched against a sitting target, and the on crit effect not seeing you as sitting when you were hit. This was a bug in vanilla, Blizzard has been actively leaving bugs and loopholes in on purpose.
Use pre-formatted text to get around not being able to post links, it’s easier to copy and paste.
Thanks will do
but you literally said that it was only on private servers - yet those videos were showing Mashing X to gain Reck charges were from retail Vanilla.
the Classic devs’ design goal was that “if it was in Vanilla, then it will be in Classic”
the ONLY way they could possibly prevent this type of mechanic is to completely remove Vanilla type Spell Batching - but as I said in an earlier post - that isn’t going to happen
The problem is, no one knows one way or another.
If you guys weren’t present for the Nostalrius development process, they way they did it was they took the stock database et al and made improvements based on the community’s effort.
So, if anyone could find absolute proof of something happening some way in Classic, it would be changed by the Nost team.
This happened for about 2-3 years, then the server shut down.
The database was frozen for a while, then when Classic was NOT announced in 2017, they assumed Blizzard had lied to them. Feeling betrayed, they allowed anyone to use the database and most notably partnered with Elysium to launch another server with their code and data.
This backfired, as it eventually came to light that Nost were the only Private Server group operating without trying to make money from it, and all their information was made private or deleted.
There is no way to go back and check their process, but one way or another, it would have went one of two ways:
The default was sitting would cause on-crit effects, and they either found no evidence that it SHOULDN’T, or they found evidence it did.
OR
The default was not working that way, and they found evidence that it SHOULD some where, and made it work that way.
Either way, I trust their exhaustive work a lot. I understand people’s skepticism especially if you were not in on the ground floor with them, but frankly they are the reason this is happening.
They traveled to Irvine and showed executives at Blizzard that it was worth making this product, and now its a reality.
All anyone should be saying here is, for Blizzard to prove these things are or are not intended, just like Nost allowed for.
If they believe sitting during crits should not proc on-crit effects, then there must be some reason why.
Explain that, and demonstrate the proof, and problem is solved.
Until then, I don’t believe they are correct on this topic, but I have no way of knowing one way or another and neither does any one else unless you guys have copies of the github and all the info from Nost or the videos / screenshots they might have used as proof.
1 Like
This footage from 2006 definitely looks like evidence to me, but you seem knowledgeable on the subject. Tell me about these private servers in 2006.
simple way to test whether it is spell batching or something else entirely
have the classic devs ramp up the Classic beta spell batching to current BFA retail values and see what happens.
if mashing X still triggers RECK/Enrage/Blood Craze procs, then there’s something else at play here
if mashing X does nothing at that point then…
and it’s Spell Batching by a nose!
Much simpler. Just test it on their 1.12 client. I assume they did test it with sitting, but didn’t go to the extent people are doing in the Beta by precisely timing standing up at the right time
Think what you’re viewing is footage from a retail server at that point.
Based on numerous posts, disscussion, and the not a bug blue the /sit per private servers where you sit and then automatically stand when hit is a bug. However spamming X or monkeynews sit>move which causes your character to alternate sitting and standing coupled with spell batching and latency produces the same effect as seen in 2006 video linked below and therefore seems to be an accurate reproduction of 1.12 mechanics. Working as intended, although unreliable at best. I’ll still be leveling as arms!
1 Like
The people trying to justify this are funny. If its a bug to allow crits to proc talent affects when sitting then its also a bug to allow it if they mash their sit to glitch the system into thinking they are sitting well standing. Easy fix is to add a 1 second internal cool down on procing talents like enrage/wreck when you go from sitting to standing. =)
that would be going against Vanilla Blizzlike mechanics my friend
#NoChanges
and these videos in particular from Vanilla WoW:
#WartsAndAll
Better than letting a bug/exploit work. That wouldn’t even change anything. “Wouldn’t be classic”?? The only thing that does is fix a bug/exploit so the server doesn’t think your sitting when your standing. Adding a one second internal delay would only stop the bug/exploit. We don’t need rets getting pre 5 stacks running around oneshoting everyone. Might be fun for the rets but it isn’t fun for everyone else.
1 Like
welcome to vanilla/classic my sweet summer child…
You really think the devs are going to leave a bug/glitch in the game that lets rets run around the world oneshoting everyone… blizzard obviously doesn’t want sitting to proc reckoning or other such talents. So you think a glitch sever side by mashing sit and running to accomplish what they didn’t want happening and fixed to be left untouched? They also said they would fix bugs if found in classic. Keep dreaming of rets running around oneshoting everyone it isn’t going to make it live. Good luck, see you in classic =)
Iffy to say if they’ll find a way to ‘fix’ it or not. Evidence shows that it did exist via spell batching, so the stated philosophy would be to keep it. Obviously, the bluepost clearly states that it will not be in Classic–but if I had to guess I’d see this as an oversight in their internal testing—they looked, though it was out, but it technically works and they’ll eventually backtrack and let it stay rather than patching it.
We’ll see
spell batching says hello my friend…
they specifically only mention /sit in the blue post - not mashing your X button to both sit + stand and use spell batching as a creative use of game mechanics
Nah, their blue post doesn’t say spell batching a stand when you get crit while sitting doesn’t work to proc effects.
It just says being crit while sitting doesn’t proc effects.
2 Likes
^^^DING DING DING^^^
Sitting isn’t a spell. It’s technically still procing because you force a crit by sitting. It makes no
Difference your just tricking the server into thinking your still sitting when your not. They can just patch it so you don’t incorrectly get crit well standing. That’s a bug in itself. Why are you being crit well your standing. You shouldn’t be getting auto crit well standing.