Page 1 of 1

[LOD] Tiket@uswest.battle.net - Perma Invs Refused Auto Attack

Posted: Mon Oct 22, 2018 2:16 am
by Yevorana
Replay Link: https://entgaming.net/findstats.php?id=11520581 OR http://storage.entgaming.net/replay/vie ... 520581.w3g
Game Name: [ENT] LoD -sds6bod2fn #65
Your Warcraft III Username: Yevorana
Violator's Warcraft III Username: Tiket
Violated Rule(s): Refusing to Auto Attack while perma invisible
Time of Violation (in-game or replay): 3 minutes and 10 seconds game time. 12 minutes and 9 seconds replay time.
Any further thoughts:
WC3ScrnShot_102118_220605_07.png
WC3ScrnShot_102118_220605_07.png (3.41 MiB) Viewed 430 times

WC3ScrnShot_102118_220611_08.png
WC3ScrnShot_102118_220611_08.png (3.46 MiB) Viewed 430 times

WC3ScrnShot_102118_220650_09.png
WC3ScrnShot_102118_220650_09.png (3.43 MiB) Viewed 430 times


I never understood the whole exploit of casting and perma invisible staying invisible thing. However, after becoming a victim of it, then I understood. Techies didn't autoattack due to scouting the woods instead of laning. Techies only auto attacked probably by accident after this incident which stopped the bug. Hard to say if it was an intentional exploit but the usage of the bug still happened at this timestamp.
I won't be surprise if the punishment is lenient quite frankly. The rules are still rules however but because I rarely become a victim of this, I decided to report it to see its full context on what happens when someone uses this bug.

Re: [LOD] Tiket@uswest.battle.net - Perma Invs Refused Auto Attack

Posted: Wed Oct 24, 2018 2:54 am
by CheW
Technically the glitch is going invis while casting AFTER auto attacking as it is supposed to (in -BO mode) not reveal while casting.

Re: [LOD] Tiket@uswest.battle.net - Perma Invs Refused Auto Attack

Posted: Wed Oct 24, 2018 7:45 pm
by Merex
Indeed, hard to tell if intentional. Nevertheless, the role that invis played in this would've been the same without this bug as you were low and a blow by a mine would've finished you in any instance. Given the bug is over after that this, will not ban for it.