Login to ZARP

TOPIC: [TTT] Warn Appeal

[TTT] Warn Appeal 5 years 6 months ago #1123383

Name - JJonGames
STEAM-ID - STEAM_0:0:141529070
Staff Members Name - Stuny
Punishment Reason - RDM
Server - TTT
Story/Situation - So this guy named kobra was shooting at the Detective and I clearly saw it. So I killed him for shooting the detective. He also never identified the body making it another reason to KOS. I don't see how its RDM.
Extra Information - Anything you would find relevant to your warning(s)? Damage logs for proof I saw him shoot at him.
prntscr.com/nsrvqd

JJonGames
Offline
Junior Boarder
Make a difference.
Posts: 163
Thanks received: 44
Karma: 0

I believe in the person that can make a difference. -JJonGames

★ Zarp Vip ★

★ TTT Administrator ★

★ Former Jailbreak Moderator ★

The topic has been locked.

[TTT] Warn Appeal 5 years 6 months ago #1123384

I'll handle this!	Rule Offline Legendary Member Kyber4PHSO Posts: 1582 Thanks received: 1260 Karma: 1
Ex-Staff The topic has been locked.

[TTT] Warn Appeal 5 years 6 months ago #1123391

Sucks dude, hope you get it removed! Unless Stuny wasn't mistaken	Davidov007 Offline Expert Boarder Expect me to write, a lot. Posts: 1590 Thanks received: 756 Karma: -44
♠ Ex-TTT Head Administrator ♠ The topic has been locked.

[TTT] Warn Appeal 5 years 6 months ago #1123394

	Kurze Offline Legendary Member Expect me to be straight to the point. Posts: 2234 Thanks received: 1039 Karma: -33
Plus Ultra! EX EX TTT Super Administrator x3 EX TTT Head Admin The topic has been locked.

[TTT] Warn Appeal 5 years 6 months ago #1123399

Hi JJonGames!

After speaking with the staff member that warned you, I have decided to Accept this appeal.
Stuny said he made an honest mistake with the logs, however, he did mention that in the response to the report, you said something along the lines of "You killed the detective" which did not happen. In fact, it was Stuny who killed that detective, which led Stuny to believe that you mistook him for the traitor that previously shot the detective, which led to your warning. I would advise being more careful with how you respond in reports so that another situation like this does not occur again.

This appeal has been:

:accepted: