Accepted Ban Request Against GUAH ON MAH DIH

Discussion in 'Approved' started by Bender, Mar 24, 2019.

Thread Status:
Not open for further replies.
  1. Bender

    Bender Forum Bot

    Joined:
    Jan 3, 2015
    Messages:
    1,952
    Likes Received:
    88
    Ban Request Against GUAH ON MAH DIH

    Target 1:
    GUAH ON MAH DIH (STEAM_0:1:77267285)


    Requester:


    Event Date and Time:
    11:23, 2/23/2019, PST
    Server:
    Devinity Flood US #1
    What rules the target broke:
    1: Do not minge or sabotage. This includes but is not limited to:
    1a: Disrupting gameplay via aimless flinging.
    1c: Trapping players + pinning boats down.
    Briefly explain what happened:
    Prop pushed people around the server, trapped me in a box until the round started.


    Screenshot evidence:
     
    #1
  2. Bender

    Bender Forum Bot

    Joined:
    Jan 3, 2015
    Messages:
    1,952
    Likes Received:
    88
    Ban Request Against Mikal Vsauce

    Target 1:
    Mikal Vsauce (STEAM_0:0:208487601)


    Requester:


    Event Date and Time:
    March 23th, 2019 ~11:20 PM (Pacific Time)
    Server:
    Devinity Flood US #1
    What rules the target broke:
    1: Do not minge or sabotage. This includes but is not limited to:
    1a: Disrupting gameplay via aimless flinging.
    1c: Trapping players + pinning boats down.
    Briefly explain what happened:
    Player was flinging the anvil/weight prop around and laying it on top of another player's boat.


    Screenshot evidence:
     
    #2
  3. counter

    counter Moderator Staff Member Server Moderator Platinum VIP

    Joined:
    Feb 21, 2015
    Messages:
    3,131
    Likes Received:
    850
    Server:
    Flood
    Discord:
    co#2858
    I was with these players and kinda spoke to them at the time when the reports were created, so I've decided to ban both of them for 20 hours instead of the regular 24. However they will be punished more harshly the next time they decide to break the rules

    Thanks for the report and I hope you don't mind with the outcome considering the aforementioned
     
    #3
Thread Status:
Not open for further replies.