+1 for the Warn, seems like the situation is simple as is. OTHER THAN THE FACT THERE IS NO VIDEO EVIDENCE, Like, perhaps next time it happens, gather some video evidence for a more clear picture. There doesn't seem to be a plausible excuse for a Jury to kill the Ranger in this situation.
-1 for the warn, I was the CWU travelling with him and calling out people for him to capture and was there when these kills happened, the first one was an accident but the second one that I saw was blatantly just you trying to get a kill as the Jury had him capped running with him, I am not saying however that he is in the right as he should not have RDM'ed but he did get CK'ed and blacklisted from Jury for his actions so to punish him more would be useless as this was handled inside the faction by his CO.
I was being shot at by the sniper, I should not be expected to let myself get killed so a JURY can cap someone. You stating that the sniper was already capped is impossible given that in the console it doesn't show ANYHWERE that the sniper was cuffed.
The sniper was capped for a second which is why it may not have popped up in the console but as I said that one was an accident and no issue, it was the second time that was the issue stated in my previous message. Like I said however it does not excuse his actions I am merely adding information that led up to these events transpiring in the first place.
The second kill was the sniper, the first one was the RU, neither capped, though I did neglect to show more of the console before I killed the RU so I guess the argument could be stated that there was no proof of that.
Discord Username: ...[X_X]*Argy*[X_X]...#8912
Steam ID: STEAM_0:0:564115838
Staff/Player's Name: NPU JURY 05 52151
Staff/Player's Steam ID: STEAM_0:1:581877224
Requested Action against Staff/Player: RDM warn
Reason for complaint? This mf RDM'd me out of pure spite because I killed someone he was about to cap (twice)
Evidence/Other:
After brief talking of the situation as a whole, We’ve come to the conclusion to deny this warn due to this already being handled IC.