False slay + double down

**frost**

Offenders Name: Rox5tar01

Offenders Steam ID: STEAM_0:0:219519159

What Server(s): TTT

Offender's Rank: T-mod

What they did: False slay

When they did it: Now

Potential Witnesses: Sal, Nico, Love4Puppys, ^aethy, murl, etc...

Recently on the server, I killed an innocent through following a kos. I got reported for it saying, "killed an innocent for no reason". I had a valid reason to kill them as they were kosed through voice chat and I simply followed it. Another staff member agreed that they were kosed in voice chat and the map changed. Once the map loaded in, Roxstar proceeded to slay me with the given reason "He said Sal shot him, and Sal responded by a KOS. / Followed Traitor KOS with no reasonable cause to believe". Given as there have been many incidents where a traitor had called a kos on someone and an innocent was killed because of it but no slain was given, I don't understand how my incident is any different. After asking Roxstar about it, they said "Sal was a traitor, so Sal can't be slayed for it. You followed a bad KOS, so you get slayed."

**3mb3ry** · 08-31-2025, 12:02 AM

it was actually ridiculous that you got a slay for that but not surprising that it was Rox5tar01 that dealt it. +1 to strike or whatever the action would be to handle this

**^aethy** · 08-31-2025, 12:33 AM

Mind blowing slay reason

By this logic I can kos 3 people as an undetected T and if 1 person were to follow it they could potentially be banned for mass

**murl** · 08-31-2025, 01:07 AM

come on man, this is a just a bad slay. You had like 8 regulars telling you this was invalid and you still went through with it. Never in the history of dinks has an innocent been slain for a traitor KOS, it just counts as a traitor kill and ends at that.

**Dinomoto** · 08-31-2025, 02:46 AM

Well this is the 2nd ridiculous reason I've seen in 24 hours.

"no reasonable cause to believe" what is that rubbish.

**Rox5tar01**

So regarding the slay, this all stemmed from a misunderstanding I had regarding the rules. My previous understanding was that if a Traitor calls a KOS on somebody then the slay falls to the killer. This especially felt true in this circumstance since the victim had said multiple times "______ is shooting me, ______ is shooting me, ______ is shooting me", followed by the KOS by Sal. While I don't consider saying "______ is shooting me" to be a KOS, there is not really any definitive definition in the rules/guidelines on what constitutes a KOS (although there is precedent) and that led into my thought process regarding whether to give the slay to you or not.

I could have sworn I have seen similar situations like this earn a slay from other staff before, but I can't remember any specific examples of this off-hand and it is very possible I misunderstood those previous situations. I will also say that I did bring this up to the other staff a bit before this post went up (after which the overall consensus is that I was in the wrong), and that's why I was AFK after the slay was given. I probably could have done a better job communicating that to you, versus making it seem like I slayed and moved on.

I've went ahead and given myself a double slay for the bad slay. I apologize for the bad slay, and will try to do better going forward.

**jonifun92** · 08-31-2025, 12:07 PM

(08-31-2025, 11:18 AM)Rox5tar01 Wrote: So regarding the slay, this all stemmed from a misunderstanding I had regarding the rules. My previous understanding was that if a Traitor calls a KOS on somebody then the slay falls to the killer. This especially felt true in this circumstance since the victim had said multiple times "______ is shooting me, ______ is shooting me, ______ is shooting me", followed by the KOS by Sal. While I don't consider saying "______ is shooting me" to be a KOS, there is not really any definitive definition in the rules/guidelines on what constitutes a KOS (although there is precedent) and that lead into my thought process regarding whether to give the slay to you or not.

I could have sworn I have seen similar situations like this earn a slay from other staff before, but I can't remember any specific examples of this off-hand and it is very possible I misunderstood those previous situations. I will also say that I did bring this up to the other staff a bit before this post went up (after which the overall consensus is that I was in the wrong), and that's why I was AFK after the slay was given. I probably could have done a better job communicating that to you, versus making it seem like I slayed and moved on.

I've went ahead and given myself a double slay for the bad slay. I apologize for the bad slay, and will try to do better going forward.

Every one makes mistakes. Thats just how it is. Frost is roght with making this ticket, and you are right by admiting you were wrong. And some people have a hard time doing so

**TDawg4** · 09-04-2025, 06:21 PM

Closing this out. No action besides the slay for making a bad slay.

Also generally, reminder to staff that the default position (tie goes to the runner) is no slay. So if you aren't sure and can't get a hold of somebody in time opt for no slay.

Reminder to everyone that following a "bad" KOS is only your fault if the person making the KOS is already called out / Is a revived Traitor / etc.