Skip to content

Sivir spellshield still blocks multiple abilities and damage

AbodyHUN666··5 votes·1,650 views

Just had a game where the enemy Sivir dove under our turret to kill me, and survived, because her spellshield blocked our Jinx's chompers and Zap at the same time, while taking no damage from either. I thought this bug/coding was fixed.

8 Comments

Sir ArmaMalum3 votes

Now I'm not a professional, but from my understanding this is an issue with the game's tic rate (<0.25 sec I believe, correct me if I'm wrong anyone). A tic rate is simply how often a game updates itself to what is happening. If two effects hit within the window of 1 tic there is no way for the game to be able to tell which spell hits first. so at that point you have two options: deny both or randomly choose between the two. Randomly choosing could easily screw over the Sivir/Nocturne/Banshee in question since it could just as easily make the spellshield useless in these cases.

tl;dr Not a bug, but technical limitations

AbodyHUN6661 votes

Still, the game needs consistency. 0.25 sec is such a small window that you can't really measure which ability hit first, blocking a random spell, or blocking the one with higher damage or stronger CC would at least make it more predictable.

Sir ArmaMalum1 votes

I'm not really understanding what you mean, as blocking a random spell instead of both would make it less consistent. Because it's random.

Blocking off of a specific hierarchy is not possible from what I understand, as it would have to pull the info of each ability and return the result in the window of less than 1 tic. As much as I would like, it all can't happen instantaneously.

AbodyHUN6661 votes

What I was trying to say is that, a human can't really determine which ability hit first in such a small time difference, so if the spellshield would block one of the two skills randomly, people would just accept that the blocked one hit first without even thinking. With the spellshield blocking two abilities at the same time and the Sivir and Nocturne getting kills because fo it, people will scream 'ty Rito you suck" like in my game. Although I'm not a programmer so I don't really know how it all works.

Sir ArmaMalum1 votes

See, the problem with that however is when a much less significant cc comes and the same time as a much more significant cc. Say you get hit by Cassiopiea Q at the same time as a Taric stun. That's a 50/50 chance of being poked or getting stunned and probably killed. The worst part being that the Sivir did use her shield, but the shield didn't block the ability she presumably used it for, the stun.

AbodyHUN6661 votes

Yeah, I know that it would feel bad for the Sivir, but in my opinion most players would just assume that the other ability hit them first. I have this issue on these spellshield champs, not reacting quick enough to block the cc, or getting it popped by some damage ability.

Sìel2 votes

{quoted}

Still, the game needs consistency. 0.25 sec is such a small window that you can't really measure which ability hit first, blocking a random spell, or blocking the one with higher damage or stronger CC would at least make it more predictable.

Yes, we can't measure which ability hit first with our naked eye.

However the coding for this does all the calculations in real time.

So in this case, the time frame of Sivir's spell shield starts as soon as the ability is activated lasting 1.5 seconds. During those 1.5 seconds Sivir can walk into the chompers being placed, which has a 0.7 arming time, (but we don't know if Sivir walked into the chompers the moment they were dropped or after so its hard for us to actually calculate that) and trigger them 0.7 seconds later OR if Sivir walked into them after being armed, then the character model and the chomper model for triggering the effect are calculated.

Now we add in Zap!, I'm not exactly sure of the wind up time but it is close to, if not exactly, 1 second. Then we add the distance it was fired from and the projectile speed, which I have no idea what it was. Anyway, the coding for all this is taken into consideration in real time as I mentioned above.

WE cannot determine which spell hit first, but the system CAN. So as Sir ArmaMalum mentioned, there's roughly a 0.25 window in which these spells were calculated in and ended up blocking both chompers and zap.

TL;DR - We can't visually process the information as fast and accurate as the system the game was designed to calculate. 0.25 seconds may seem impossible to visually see what hit first to us, but it is easy for the system to determine it.

But yea, this issue has been around for a while and maybe has been looked at. But Rito does things their way and we kinda have to be patient about it unfortunately.

kDrakari1 votes

Spell Shields blocking multiple abilities that hit at the same time, while not necessarily "intentional" in the strictest sense, is not considered a bug. The bug that existed was that Spell Shield was previously blocking EVERYTHING that hit in a single frame (or tick, if that's the case) including auto attacks, and the fix made it no longer block auto attacks.

More from Report a Bug

More by AbodyHUN666