Left game "Akitos" (ban request)

[oxoDus]

Hi,

s2 game was hosted and Akitos signed into it. Skillerinstinct disagreed to unhost so i started. Then Akitos left in game. You can read the chat yourself. So i request 3 days ban + dc penalty. (He knew the consequences because he banned me the same way)

akitos quit.w3g

(37 KiB) Downloaded 41 times

EDIT: (ent link to the game if it's easier: https://entgaming.net/findstats.php?id=2973542 )

[JunZzi]

Akitos unvouched for 3 Days for leaving the game.


The rule is as follows:

[spoiler=]ALL players must be in game before any swaps are made.
ALL players must agree to the swap.
Any flaming/abuse/'convincing' with regards to getting a player to agree will not be tolerated.
Players have the right to disagree at ANY time. That means if a players agrees in the channel then he does not need to agree in the lobby. (I would hope noone is immature enough to do this)[/spoiler]


EDIT:

After further Discussion with Iighfyre the ban stays for the following reason:

You have to have 100% Players to agree on Swapping, If one player disagrees, Then the game can be started, You cannot leave based on a agreement that 4 players had before the game was signed, If one player decides to change his mind, Then NO means NO, and the regular leaving rules are in Effect.

[iightfyre]

!support this ban

After reviewing all of the evidence, I believe that Akitos should have played the game out as clearly stated in the rules of the LIHL.

Remember a few things here:
Anyone has the right to refuse a swap. Whether or not an "agreement" was made prior to hosting a game.
Everyone must play the game in its entirety once they have !signed for it. No exceptions outside of major life circumstances.
No one is forced to draw a game unless there is a DC prior to lvl 20. This includes; not liking your team, forgetting to build, not liking your towers, accidentally selling a tower, etc.

We are working with uakf.b to get the functionality of !challenge2 and !challenge3 working so that we can avoid this in the future. It is for precisely this kind of circumstance that can be avoided with the proper use of the !challenge function.