ENT Gaming

Replay Link: http://replay.garena.ro/view_replay.php ... 170072.w3g
Game Name: [ENT] DotA ap us/ca #93 // https://entgaming.net/findstats.php?id=4455895
Your Warcraft III Username: campsite@useast
Violator's Warcraft III Username: jkim@uswest.battle.net
Violated Rule(s): Maphack
Time of Violation (in-game or replay): 3:00 - 4:00, 16:00-16:40, 34:47.
Any further thoughts:
At 3:47 bh changes direction, pudge follows. At 3:50 bh changes direction again, pudge cuts him off and follows. Once again at 3:53 bh changes direction yet again and pudge follow for the kill. 3 changes in direction completely mirrored is highly suspicous.

At 16:00-16:40 pudge goes directly to bh who is creeping a camp and dusts+ults for the kill.
(19:21) JKim: ward
(19:28) campsite: obvious ban
(19:32) campsite: that will be applied to you
(19:34) GodIsImaginary: see, he says he had a ward
(19:38 / Allied) campsite: he didnt
Upon review I see that the sentinel had no wards at the time. Just as I suspected, a complete lie. Which is exactly my thought when he follows me over 3 direction changes at the start of the game.

And finally at 34:47 he goes along the side and makes sure he dusts in range of BH.

After reviewing it, jkim never hided it at all.

At 6 minutes (Elapsed replay timer), he goes top to eventually gank, he notices gondar on his way in scourge forest, near top tower, so he decides to follow gondar - Seems logical; At 06:19 Gondar was already invisible and turns around (no possible sight for butcher), yet he turns around and follows gondar, at 06:24 hes still following gondar and starts rotting when he gets precisely near gondar; at 06:27 - Gondar still invisible during the entire encounter, and turns around to another direction, yet butcher follows precisely gondar positions with no wards, dusts or anything that could tell him gondar changed direction.

At 16:40 - Butcher goes straight into sentinel forest, and directly into gondar creeping spot, as if he already knew gondar would be there (There was no wards during or before gondar started creeping, so when JKIM said: JKim: ward , this is false. Yet he ran and his intentions were clear: He went there on purpose to gank gondar.

At 34:00 minutes, Gondar attempts to backdoor but failed due to backdoor protection (Rax started healing) and once butcher hooks one of his creeps (failed hook on gondar), gondar goes afk and goes near trees in sent base. Here i could call it a lucky shot, even though noticing throughout the game, it sounds he knew you dind't run off:

- Gondar goes invisible and runs right, while fading so most logical reason would gondar was hiding, still gondar could have turned around after fading. Butcher simply stops at the trees, outside of the base and dusts, revealing gondar and with kunkka, both noticing gondar was still inside base.

Considering the first 2 instances, i have no doubts that Butcher (Jkim) hacks due to suspicious gameplays.

Checked another game of him, in arem us/ca #75, at 07:10 (Elapsed replay timer), he (Jugger) simply tp tops and moves to goblin laboratory shop but decides to enter through top section, as if he knew theres mines in the bot entrance and goes straight for centaur, as expected that centaur would be there. After the incident, it's obvious he dind't knew about the mines placement:

5:51 [Allies] JKIM (Juggernaut): why he is the
5:57 [Allies] WarteUwagi (Harbinger): mines there
6:01 [Allies] JKIM (Juggernaut): k
6:04 [Allies] JKIM (Juggernaut): tnx

Banning jkim@uswest.battle.net for 1 year.

Thanks for posting

Moving for confirmation

@Hyorinmaru.

06:10-06:30 incident where pudge ganks top is suspicious. After he hooks while invis, he loses sight of bh who wws. Yet, he is able to react and follow him for quite a while. This one is pretty blatant.

18:55-19:05 bh gank incident is weak, reasonable gank due to bh's prior activity at bot lane. Pudge does lie though about wards.

36:50-36:59 incident is weak also. Pudge's dust does hit bh, so he was visible the entire time. Nothing suspicious.

I only watched the time stamps provided, but the 6 min incident looks blatant, so Ill process this.

No dodge.