Accepted Couple of Jokers (1 Viewer)

Status
Not open for further replies.

PistolPoppinSince02

Active Member
Donator
Joined
Feb 27, 2022
Messages
101
Number One; kason
  • Current Steam name.
    kason
  • SteamID (Unique ID on HlStatsx).
    STEAM_0:0:161007030
  • Which server the rule was broken on.
    U.S JB
  • Any useful links such as their HLStats profile / SourceBans search
    Chat Logs; https://hlstats.panda-community.com/hlstats.php?mode=chathistory&player=1741654
  • The rule or rules they broke.
    Blu teamkill and attempted blu freekill. Also a little too toxic for a Saturday night
  • The evidence that they broke the rule or rules above.
    Video for teamkill, and chat logs for toxicity. The toxicity borders on just malding, but the teamkill is undeniable

    Number Two; The man behind the slaughter

  • Current Steam name.
    The man behind the slaughter
  • SteamID (Unique ID on HlStatsx).
    STEAM_0:1:582291002
  • Which server the rule was broken on.
    US JB
  • Any useful links such as their HLStats profile / SourceBans search
    HLStats, Not Much here but y'know; https://hlstats.panda-community.com/hlstats.php?mode=playerinfo&player=1217085
  • The rule or rules they broke.
    Yet another Accidental Freekill (he has also freekilled intentionally before which I'm sure many can attest to, just not when I was recording)
    HOWEVER; He was warned by an admin prior to the clip that his next freekill would be a teamban, accident or not
  • The evidence that they broke the rule or rules above.
    In the clip provided he accidentally kills a red who finished obby in time, alongside a red who did NOT finish in time. One kill was okay, the other was not.
 

Attachments

  • kasonteamkill.mp4
    6.1 MB
  • Themanbehindtheslaughterfreekill.mp4
    3.5 MB
The man behind the slaughter has already been banned in a recent Black_ post, so feel free to disregard it.
 
  • Old
Reactions: _Black
Kason was already teambanned in game by me, but ill go ahead and apply the gag

Looks like man behind the slaughter already caught a teamban based on a different report.

Thanks for the report.
 
Status
Not open for further replies.

Users who are viewing this thread