[LTD] ltd mega #94. whole team.

[Wake_N_Bake]

Your Warcraft III username: Wake_N_Bake
Violator's Warcraft III username: tofudobeast@ueseast , daihelyon@europe , marlezo@useast , armedanddeadly@europe
Game name or map name: [ent] legion td mega #94
Stats page link:
Rule player violated: paused game purposly in the middle of sending.
Time of incidents (Note in-game timer or replay timer):
Any further thoughts: they sent hard on lvl 26. we were saving for lvl 28. they clearly knew this as they werent average pubs. they paused in the middle of our game ending send making it unable for me to fully build as merc. no questions about it it was on purpose. they claimed that teammate was afk because he had 2k lumber saved up. they had just sent on 26 n only person who sent on 28 was yellow. so him having 2k lumber doesnt make him afk. plus they just happened to notice it right as they knew i was making last moves as merc to send hard n build hard? convenient. they all need to banned for atleast a week. please watch replay and make appropriate judgement.


--- Wake ---

[Daihelyon]

Your Warcraft III username: Daihelyon

The game in question: https://entgaming.net/findstats.php?id=2236600

In our defense: Around 53 minute in game time I fell a sleep for like a few minutes (playing from Europe, and the real time was 3 am, I thought the game would end earlier and didn't think that I am that tired until we reached round 17 something), and when I "woke up" (not a real sleep and not a real waking up, but a "what, where, huh?" state) and I looked at the timer and it was like 10 second to start round 28, saw the votekick and pause, knew that I didn't build (you can check my gold and lumber), and I panicked a little, tried to unpause to build, but couldn't. It is just a coincidence that we won. I would suggest to delete this game from all of the participants stat (or make it a draw, although others, and I would bet anything that Wake_N_Bake is like them, wouldn't move their fingers if they had an easy win like this, and would do anything to keep it on their stats).

[Wake_N_Bake]

If u were afk for that long then they were enjoying a nice feed all game. They said nothing all game and asked for a vk just before lvl 28 sends hit. They knew they lost n tried to prevent by pausing game. Bottom line its shady n deserves a ban.

[HateLose]

@Wake_N_Bake Did you watch the replay like you said you would ingame? Just curious....
Also I noticed you only had about 300 lumber right before the round started. How were you planning to build max (as merc) with such low lumber? Don't blame the pausing on the building, because you clearly didn't have enough lumber. I'm guessing because the pausing you might have oversent? not sure....

Anyways...after reviewing the replay, this is interesting. Orange (daihelyon) did go afk after 26 started (so it seemed). Their team didn't realize he was afk until 28 started, because they kept asking teammates to send and noticed he had about 2k gold and 2k lumber. I wouldn't ban anyone except Orange (daihelyon). Why? After reviewing the replay I found some interesting things. See Below.
Please ban daihelyon for MH.

Thanks for reporting Wake_N_Bake

[supersexyy]

Not sure of the full details but I think some Prophet clicks can be bugs.

[HateLose]

I'll rewatch the replay when I get home and confirm it again.

[Wake_N_Bake]

No i did not waste my time wathing the replay. The game was shady n i posted. Ban or no ban its w.e just like pointing out shady players. I would gadly play them again even if they choose to mh.

[Iznogood]

Not sure of the full details but I think some Prophet clicks can be bugs.

They are bugged often @ prophet - but the "fogclicks" normally start early in the game.
I can't check it before tomorrow.. maybe someone else can

[Wake_N_Bake]

Any tips on detecting map hacks while watching replays. Ive never really understood how to detect.

[niho]

how to detect MH--->>>> viewtopic.php?f=8&t=7086, its 1 of the top threads in request ban

[HateLose]

My bad...been a lil busy, but here is more proof.

0:21 |cFFFFA500Daihelyon|r clicked Prophet (this one might be a bug)
6:18 |cFFFFA500Daihelyon|r clicked Prophet
43:39 |cFFFFA500Daihelyon|r clicked Prophet
58:9 |cFFFFA500Daihelyon|r clicked Prophet

[bit]

all 4 fogclicks are bugged. denied