[LOD] Tiket@uswest.battle.net - Perma Invs Refused Auto Attack
Posted: Mon Oct 22, 2018 2:16 am
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:
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.
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:
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.