Invalid Report against Gunandbomb

Discussion in 'TTT Staff/Player Reports' started by acer8, Oct 6, 2016.

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

    acer8 VIP

    Name of Staff/Player:
    Gunandbomb
    Steam ID of Staff/Player:
    STEAM_0:0:66787251
    Your Steam ID:
    STEAM_0:1:20382393
    Which Server:
    West 1
    Which Map:
    assault
    Which Round:
    2
    Time of Occurence:
    1:40am eastern roughly
    Reason For Report:
    If you go back and check the shot logs for that round you will see I hadn't fired a single shot after killing the T. Gunandbomb took it upon himself to allow him to attempt to loophole and used the 5 second after iding a body rule to justify the killing. To my knowledge, a mod or admin has to take the response as is and can't just justify it by their own means.
    [​IMG] [​IMG] [​IMG] [​IMG]
    Evidence And/Or Witnesses:

     
  2. Steve Mason

    Steve Mason Honesty. VIP

    Tagging @GunAndBomb and his admin @Lemon, please wait patiently for Gun's response

    Thank you.
     
  3. GunAndBomb

    GunAndBomb Explosive VIP

    I will respond when I am done staffing.
     
  4. GunAndBomb

    GunAndBomb Explosive VIP

    Ok, so let's get right into this.

    This is a simple '5 second rule' situation which is defined as:
    [​IMG]

    This is not loopholing, which is:
    [​IMG]
    He did not avoid punishment as he did not break any of our rules, since his actions are protected under the 5 second grace period.

    @Lemon will determine the verdict.
     
  5. Lemon

    Lemon ideal male moderator VIP Silver

    Acer,

    Thank you for taking the time to report my moderator. In the report you claimed that you were killed for killing a Traitor. While that may be a frustrating situation, it is not RDM nor is it loopholing. Shooting towards another player is considered a traitorous act. Since you were shooting, those bullets could've gone towards the player who killed you. With that said, I will mark this report invalid. Feel free to PM me for further questions.
     
    Last edited: Oct 7, 2016
Thread Status:
Not open for further replies.