[LTD] uncle didnt build at all 12 with ea when we had free win

[Viserion]

Replay Link: http://storage.entgaming.net/replay/vie ... 736457.w3g
Game Name: [ENT] Legion TD Mega 1200+ #4
Your Warcraft III Username: Viserion
Violator's Warcraft III Username: Uncle
Violated Rule(s): game ruin tk due to no build
Time of Violation (in-game or replay): 24 min
Any further thoughts: u just need to watch replay once... we died very close lvl 12 cause of him not building at all with ea. uncle had 1355 value for arena with ea... he stayed 1355 for 12 also so didnt build at all for 12.. we died due to that.. ofc we 100% cant die if he build... it was even close with him not building at all..
Thank you
Zevex

[JoanBaez]

I thought I upped Ea, and focus 2 spend all wood, but I didnot upgrade, misstake of me

[KiwiLeKiller]

It was a mistake, obviously. Your plan was shit, he wouldn't have mid anyway. You need to learn the game.

[Viserion]

What he said is not an excuse.. I mean he has 1 min to build... he has ea... u can expect from a experienced player to be able to build eas for 12 with 0 heals. and he also said "they did dinos arena" etc.. he was just totally wrong that they cant send 12 so that was the reason for no build to send some more which was ofc not needed at all. they die anyway... he was totally wrong they cant 12 and that was only reason we lose this game. so game ruin and tk at its best obviously.

[Viserion]

and failing is 1 thing... everybody fails sometimes. but if a fail is huge like this AND it ends with loss instead of free it was in this game its more than a simple fail because he made 3 guys lose due to total unnecessary no build with ea for 12.. i mean wtf.. there is absolutely no reason not to build for 12 with ea and -4 when other team is 100% dead due to huge send from us...

[SnowwyWolf]

Blaming green for this loss is ridiculous if he upgraded to EA and went full build you still would have probably lost the game on that round, regardless we do not ban people for making such an easy mistake here. I will, however, put a warning to make sure it isn't a common occurrence (which I'm sure it isn't).