Login to ZARP

TOPIC: dlt pls

dlt pls 5 years 1 month ago #1091345

delete pls	KrecikS Offline Fresh Boarder Earth is flat! Open your eyes Posts: 75 Thanks received: 4 Karma: -3
Last Edit: 5 years 1 month ago by KrecikS. The topic has been locked.

TTT rules 5 years 1 month ago #1091351

If someone has been KOS'd then its a valid reason to kill them. So for say, innocent KOSes innocent and other innocent kills the KOS'd innocent then Innocent who called KOS is also KOS. Yes confusing. What are you trying to say you got warned for killing someone who was KOS'd?? After reading this again I'm bamboozled..	Kurze Offline Legendary Member Expect me to be straight to the point. Posts: 2234 Thanks received: 1040 Karma: -30
Plus Ultra! EX EX TTT Super Administrator x3 EX TTT Head Admin Last Edit: 5 years 1 month ago by Kurze. The topic has been locked. The following user(s) said Thank You: Jim_Jam

TTT rules 5 years 1 month ago #1091352

Your scenarios don't even make sense	Nina Offline Legendary Member 「(°ヘ°) Posts: 1088 Thanks received: 889 Karma: 25
Former ✯Zarp Slave✯ Last Edit: 5 years 1 month ago by Nina. The topic has been locked. The following user(s) said Thank You: Jim_Jam

TTT rules 5 years 1 month ago #1091353

Damn.	Jim_Jam Offline Former Community Manager TTT is my child ❤️ Posts: 8585 Thanks received: 3491 Karma: -32
The topic has been locked.

TTT rules 5 years 1 month ago #1091354

Nina wrote:

Your scenarios don't even make sense

The first one does, basically someone called a false KOS (but valid reason) on another player, a random player kills the person with the KOS on them, to which he just killed an inno, so the player that got KOS'd reports the person who killed him, not the KOS'er

I think the second version is the same except the T kills the inno, to which he said could be classed as T baiting from the person who called the false KOS.

So I think OP(KrecikS) is wanting False KOS's to be punishable or made clearer in the rules? I'm not too sure but that's my decryption

CeeZee
Offline
Expert Boarder
999
Posts: 1231
Thanks received: 678
Karma: -38

The topic has been locked.

TTT rules 5 years 1 month ago #1091355

Ok. if any player calls a KOS on another player (barring detective) then that person is now KOS. The person who kills the KOS'd player is not at fault for RDM as they were following the KOS rules. The player who originally called the KOS is at fault if the player who was killed did nothing wrong.

Im assuming this has been made in response to a warn.
If so, please make a Warn appeal using this link
= zarpgaming.com/index.php/forum/appeals/4...ment-appeal-template

Please supply relevant evidence of chat logs from the round in question, as the Forum staff will need this in order to validate what you are saying.

If anything i said regarding the rule on KOS is unclear, please refer to the TTT updated rules using this link
= zarpgaming.com/index.php/forum/ttt/46862-ttt-server-rules
Or ask any member of staff who is online at the time, they will be more than happy to help as it makes their jobs easier

Have fun

edit: upon re-reading your post again, i think you need to make an attempt to simplify your scenarios a tad, theyre a bit jumbled and make it difficult for staff to determine what you are asking.
So for ill try to summarise.
Scenario 1 - Player B is committing RDM as they have no reason to kill player C, as the only thing they did was ask for a reason.
Scenario 2 - Player B is at the one who would be reported, as they were the one who called the original KOS. Player D is not at fault for killing player C as they just followed the kos.

conor.martin838
Offline
Junior Boarder
Ex TTT Staff
Posts: 275
Thanks received: 46
Karma: -1

fastdl.friendlyplayers.com/siggen/darkrpbase/76561198435750578.png

Last Edit: 5 years 1 month ago by conor.martin838.

The topic has been locked.

TTT rules 5 years 1 month ago #1091358

CeeZee wrote:

Nina wrote:

Your scenarios don't even make sense

The first one does, basically someone called a false KOS (but valid reason) on another player, a random player kills the person with the KOS on them, to which he just killed an inno, so the player that got KOS'd reports the person who killed him, not the KOS'er

I think the second version is the same except the T kills the inno, to which he said could be classed as T baiting from the person who called the false KOS.

So I think OP(KrecikS) is wanting False KOS's to be punishable or made clearer in the rules? I'm not too sure but that's my decryption

What I meant by it not making sense is that in the first scenario

"Player A calls out KOS on Player B so Player B kills Player C."

The KOS'd player B killed player C who asked for the reason for KOS'ing player B.
This would just be pure RDM as player C did nothing other than asking for a reason?

As for the second scenario it's rather confusing because of this statement:

"so the KoS should count on the person that killed, I mean if person got killed cuz he got KOSed, he should go report the man he KOS'ed."

as they're kinda contradicting each other.

Nina
Offline
Legendary Member
「(°ヘ°)
Posts: 1088
Thanks received: 889
Karma: 25

Former
✯Zarp Slave✯

Last Edit: 5 years 1 month ago by Nina.

The topic has been locked.

The following user(s) said Thank You: Jim_Jam, conor.martin838

TTT rules 5 years 1 month ago #1091376

You said 'There are 3 people' and then you list 4?!? autism intensifies	House Offline Legendary Member The best thing on Earth? Coffee. Posts: 1026 Thanks received: 541 Karma: 3
⚕ former TTT Server Owner ⚕ ⚕ former Surf Administrator ⚕ ⚕ former SSRP Moderator ⚕ ⚕ former TeamSpeak3 staff ⚕ ⚕ former Forum staff ⚕ Add me on Steam! #uzi4CM The topic has been locked. The following user(s) said Thank You: Nina, Kurze

TTT rules 5 years 1 month ago #1091393

Lol wtf	Zikinan Offline Banned Are you sure about That Posts: 135 Thanks received: 20 Karma: -6
The topic has been locked.

TTT rules 5 years 1 month ago #1091447

I had a seizure trying to read this	Slitheeeeeeeeeeeen Offline Senior Boarder Posts: 460 Thanks received: 115 Karma: 0
giphy.com/gifs/ajUY8svWJJffW/html5 The topic has been locked.