*Cyclone Exploit, GGG Please Read* Perma Cannot be Stunned and Knocked Back Bug

Edit - ***Not sure people realize how game breaking this is.

You can cyclone while taking out the gem, the first couple seconds of a pvp match, with any build (weap swap for caster/bow/etc...), and have stun and knockback immunity for the rest of the match/remaining rounds.

This needs to be fixed ASAP.***

I'm posting this in the bug reports forum as well. I think it remains relevant to pvp since cyclone is becoming more popular in LLD, the past couple days.

I was just told by a friend then confirmed through testing, that the cannot be stunned effect artificially remains under at least 3 of the following conditions.

1. Killing someone while cycloning.
2. Getting killed while cycloning.
3. Removing the cyclone gem from gear while cycloning.

After the first 2 conditions, the cannot be stunned effect remains permanent for the rest of the remaining rounds.

After the 3rd condition, the cannot be stunned effect is immediate and persists for the rest of the match.

Also... in addition to not being stunned, one also gains the ability to not get knocked back. Heavy strike for sure, and maybe other skills with knockback will no longer have this effect for the rest of the match.

The cannot be stunned effect will show in the defense section of the C sheet. There isn't however any indicator of the cannot be knocked back effect on the C sheet. That appears hidden.

The testing conditions occurred with one level 28 challenging another level 28 to 1v1. Others are welcome to test other conditions in which this bug may occur.

bumping up this needs to be on the priority list.

Not sure people realize how game breaking this is.

You can cyclone while taking out the gem, the first couple seconds of a pvp match, with any build (weap swap for caster/bow/etc...), and have stun and knockback immunity for the rest of the match/remaining rounds.

This needs to be fixed sooner than later.

Btt.

This needs fixed asap.

Bump, to get a GGG response about this exploit.

Um, holy shit. This deserves more bumpage (if true, but I'm lazy so I'll just trust you)

Bump for GGG to acknowledge this exploit.

bump

This has already been fixed.