[Approved] Ban/Timeout request on HighlandCharge

[Buhan]

Offenders in-game name: HighlandCharge

Your GUID / Name in-game (optional): Buhan

Date and hour of your ban/mute (UTC/GMT) - (DD/MM/YY): 15:30 - 16:00 GMT

Their Crime: Made his bots charge on purpose at the beginning of each round unnecessarily then suiciding/leaving immediately then joined again when the round was over and repeated.
                      He did this atleast 4 times in two matches, check the logs.
                      It sucked for the rest of the team because we were down by one regiment and lost each time.

Evidence: Check the screenshots, Took them early at first round

[Thundgil]

Hello Buhan,

this case in under review.

[Thundgil]

Hello Buhan,

after checking the logs that day player in question seems to have trouble with the game an looses connection very often. We will check next days if that continues before we can make a decision if its probably on purpose or a technical error.

Respectfully,

T.

[Buhan]

Hello again

Wanted to give an update and tell you that this person still does this.
Just now we played on Russian side, he picked militia, ordered them to charge and immeditaly disconnected and reconnected and again same thing next match. It's frustrating to see a teammate waste troops like that.
Furthermore I would argue that he honestly does this on purpose because

a) The player has a ping of 33 which is a indication of a good internet connection.

b) The player literally has 'charge' in his name which tells me he's just meming on us

As of writing this post I took these screenshots. he picked Hussars, made them charge, most died before getting a kill and he as usual left and rejoined.

[Thundgil]

Hello Buhan,

since it happens still and again (I´ve seen your notices in discord also) we will keep this player back from server now.
If it is only a technical error the player in question can come here and will get help. If not - he dont deserve to disturb the game for all others.

Request approved - player banned.

---

Short update: Player did it on purpose - no technical error. Saw on server before the logban.