Current behavior: Pyroclasm proc .5 - 1 second after the soulfire hits the target.
Intended behavior: Pyroclasm procs immediately after dmg from soulfire is dealt.
I have noticed in PVE & PVP that the pyroclasm proc is 100% consistently delayed… A rogue or priest for example can (likely) vanish in the lag proc time, or put up a shield where they shouldnt be able to cause stunned (except orc ofc).
I havnt seen anyone actually do this (prolly cause they are a bit slow) but I dont see why it wouldnt work. I’ll see if i can get a video of it. Anyone else noticed this annoying (not original) behavior?
I have a feeling this “delayed proc” has something to do with the “fake lag” spell batching of 400ms.
PVE proc delay - https://youtu.be/h-fYPXXnp-I
Here is another video fully displaying what I am talking about.
The Rogue is able to vanish before the pyroclasm proc occurs. It still occurs while in vanish, but it should take effect immediately after the soulfire impact - https://www.youtube.com/watch?v=Ka21l6YE2lc
Player able to run out of range of immolate cast because of delayed proc while running on mount - https://www.youtube.com/watch?v=HND95-ILjIA
----edit 5.20.2020----
Pyroclasm is still a bit broken. Still has a delayed proc stun - (allowing opponents to get off an action or two before the stun proc occurs).
Is this stun delay due to batching?? If so, probably will never be fixed… I dont expect any response, but just posting here for proof if anyone ever decides to do some work on bugs and stuff :).
1 Like
I believe it. So many things have the timing messed right up by this fake-lag BS they’ve tried to implement. Half these bug reports would never have been made.
4 Likes
Batching has existed in every version of WoW, and most online games use some sort of packet system.
What they did, if I remember correctly, is they added an artificial delay through deprioritizing using the current, or legion, batch system.
And there has been complaints ever since.
1 Like
It makes me nervous that they’re trying to fix the bugs this has caused but not actually acknowledging that this is the issue behind them.
I know.
They messed it up. I’ve made threads about it. Others have made threads about it, etc. Batching is fine, screwing it up - isn’t.
https:// i.postimg.cc/3R2Ng6bm/ GMresponse.jpg
Received the above GM response… sadly i dont think the GM is aware of how aware I am that this is 99.9% a bug…
The GM didn’t seem to comprehend that DR or Gear should not have any effect on WHEN the stun is applied. In this case, the bug is that the proc goes off after a .5 second delay (allowing an opponent to get an action off) when their shouldn’t be a delay on the proc at all.
*Yes - pyroclasm has a roughly 1/4 chance in proccing. You can see it proc (or not) based on if the character is stunned or not.
*My target (the rogue) is a friend of mine. I’m aware of his talents and none of them effect stun & neither did his gear.
*No DR in any of the clips posted.
Thoughts??.
My thoughts is that the GM’s don’t even know how the old game used to play. They just assume since they have this “reference client” that nothing can be broken.
Ya, thats a really irritating and unhelpful mentality to have.
Its really detrimental to people that legitimately care about original WoW mechanics.
Kinda looks like he just didn’t understand what he was seeing and what you are trying to convey, though.
Ya it appears that way… Did i word things in a confusing way???
I linked him to this thread in reponse.
I think the issue is that a lot of these bugs aren’t really bugs with the talents and spells themselves, but rather cause by that weird simulated lag they’re trying to re-create with the spell-batching.
yES THAT is exactly it.
I wish they would just be like “we are aware that out batching implementation is causing numerous bugs (list examples) and we are working to have these fixed (date/phase)”
Its irritating to see the plethora of bugs posted in this forum that are 90% caused by the above.
Blizzard, Please just admit this (incorrect spell batching implementation) reality so we (real vanilla players) can have some hope for the future.
Wow that is flat out wonky
Question: Do you think they actually have a reference client? I’m starting to think they don’t. /tinfoilhat
GJ Blizzard! This bug seems to be fixed (IN the BGs @ least, havnt tested in world yet).
Please include fixes like this in the patch notes next time though.
1 Like
TY for fix.
Plz add to patch notes next time. TY!
Edit - Proc seems to occur ~.5 seconds BEFORE the damage is dealt.
Not sure why the proc occurs BEFORE instead of instantly, but its an improvement.
I say 90% fixed.
