Spiral Knights - Please fix the stunned gunner bug, it's been around too long.

Please fix the stunned gunner bug, it's been around too long.

4 replies [Last post]

Wed, 05/02/2012 - 04:58

Pawn

Not quite sure when it got bugged (it didn't start off this way to the best of my recollection). When you shoot the blitz needle at vana, if he smacks u in the face with his mace after your charge attacks end it freezes u in place (in a moronic gun up in the air stance) unable to move or remedy for a solid 1-1.5 seconds. It's a bit ridiculous. And a lesser point of contention with me on this is that it's a bug that effects gunners adversely and hasn't been addressed in a solid 3-6 months now.

Also, i'm pretty sure this happens anytime you get hit with a stun attack when it is time to reload with any gun. Your knight just stands there completely unable to perform any action (INCLUDING REMEDY!!!!).

Wed, 05/02/2012 - 10:17

Trying

Search up stun-lock

Wed, 05/02/2012 - 10:49

Diamondshreddie

yupp

this also happens if you are stunned upon releasing the charge of a sword in the Troika line, you become stun-locked in an odd stance.

i do hope they fix it soon

Wed, 05/02/2012 - 13:42

Rommil

i wouldn't mind,

seeing this fixed.

Thu, 05/03/2012 - 04:24

Blitzwingoo

This bug appeared after a

This bug appeared after a patch back in Oct or Nov 2011. I posted about it in Dec here: http://forums.spiralknights.com/en/node/36732

The Stun lock happens when you're shooting the charge attack from a Blitz Needle or Argent Peacemaker and get stunned while doing so. As far as I can figure it's because when shooting the charge attack of the Blitz Needle or AP, you can't move until done shooting....the stun doesn't cancel this, making you get stun locked.

Back then I've submitted so many bug reports about this with no response, I finally submitted a support request on Jan 06, 2012 about it to ensure they heard about it. I asked them if this was a bug or not, and if they intend to address it if it's a bug.

The Response:
Aphrodite - Jan 06 at 8:22am:
If you have sent in bug reports about this previously, then we are aware of it. I do not know if that is intended or a bug, but I will pass this along to ask the developers.

So yeah, about six months later no fix nor a word about it.