- This topic has 1 reply, 2 voices, and was last updated May 27, 2022 at 9:57 am by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- The topic ‘squall force send’ is closed to new replies.
First Blood Gaming › Forums › Leagues › Legion Tower Defense › Legion TD League (FBG LTD) › Ban Requests › Processed Requests › squall force send
Your Warcraft III username: bad
Violator’s Warcraft III username: squall
Violated Rule(s): force send
Time of Violation (in-game or replay): 32 min
Additional Information:
https://wc3stats.com/games/247478
30:40 Allies Hectic if sebass leaks 12-13
31:15 Allies Squall go 13
31:16 Allies Squall ?
31:18 Allies Hectic nonon
31:24 Allies Squall they bad
31:26 Allies Squall we good wood
31:49 Allies Squall they leak
31:51 Allies Squall go ?
31:55 Allies Hectic i would not
32:01 Allies Squall behe merm
32:10 Allies Hectic just 15
32:13 Allies Hectic dude
32:20 Allies Hectic wth
32:20 Allies InnaDiLights xd
32:42 Allies Hectic why force?
Hello gentlemen. That is a clear case of forcing.
Solo Sending Rules:
[….]
In the case where the majority of the team is against your call or you cannot come to a consensus, do not force your own call by sending before the discussion is finished. You should give enough time for players to object to your call before sending. […]
There were 2 players clearly opposing your call and you had more than enough time to think about 13 send (as you can do it even after income) Fortunately this didn’t shape the outcome of the game but was pretty close.
As it is your first violation and there wasn’t a drawback it would be the minimum ban for solo sending.
Banned for 4h, Processed
M | T | W | T | F | S | S |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | |
7 | 8 | 9 | 10 | 11 | 12 | 13 |
14 | 15 | 16 | 17 | 18 | 19 | 20 |
21 | 22 | 23 | 24 | 25 | 26 | 27 |
28 | 29 | 30 |
Loading...