if Aithead has said something about the TK stuff then i honestly dont know cuz its clashing with the RDM stuff id honestly wait untill a HGM or HA replies but as for my response on this my answer's are based on the evidence in the clip is all nothing more.
+1 we were told in the past, both by our high command and the high managment of staff that we are allowed to TK people who spawn camp, and in the clip provided, that is an obvious spawn camp.
This is not a review of the appeal. I am clearing up a minor misconception here.
When handling spawncamp situations (and for things in general), GMs are not required to switch to the Staff-On-Duty (SOD) whitelist.
It is heavily encouraged, and there are benefits to being on the SOD job which make it worthwhile to do so (Ex. being unable to get cuffed), but it is not a requirement.
-1,
Arguments regarding the punishment sheet notwithstanding, (as that is a separate issue) TK without a legitimate reason as explicitly defined in the rules or as set by precedent (it has been a long standing precedent that SU are allowed to kill captured rebels though it is not explicitly stated) is against the rules.
Being that it is common knowledge that the rules of the server trump factional rules, not to mention the stupidity of responding to rulebreaking via rulebreaking, rules of the faction aren’t an excuse as Oil said. By the way, there are no factional rules in the resistance that support tking people who break the rules so idk where you get off saying “both factional co teams support it” lol.
As far as what I’ve seen in this forum post, no one addressed the fact that you could have asked in team chat to stop spawncamping, or that you could have ran up to the individual recording this to tell him to stop or face a demotion (as you are in your power to do based on the relatively new combine demotion policy).
TKing spawn campers is not how you should deal with situations like these, you could either:
A: Tell them to stop
B: Call staff and let them deal with it from there
Even if you TKed to deal with a rulebreaker doesnt mean that you didnt just break a rule and that you wont be punished for it
(30 Aug 22 at 10:12pm)Blims Wrote: This is namely because of one factor: Part of the 3x RDM is for something from 6 months ago (which was under exceptionally debateable circumstances considering the time period, the people, the ranks, etc.)
To list the 3 warns that got Ozz this 1 week ban they are from: 1 - April 30th 2022 2 - August 28th 2022 3 - August 30th 2022
All of these were RDM warns, and with how the punishment sheet works it scales in increments where warn 1 is nothing, warn 2 is a 2 day ban, warn 3 is 1 week and so on.
warns with ID of 6071 and ABOVE are permanent, (ozz first RDM warn has an ID of "6439" which is why he got his 1 week ban) this system is here to give harsher punishment on repeat offenders. think of it like this, i could MRDM 1 time, get a 6 week ban, then if warns reset i could MRDM again and get a 6 week ban again. this one of the reasons why we keep warns as permanent
(30 Aug 22 at 10:24pm)ozz12231 Wrote: TKing a spawncamper was encouraged by the CO team
its either report them to staff / TK them and look if they do it again / report to their COs
we do not encourage players to deal with rule breakers by themselves, if you see someone breaking a rule you can make a ticket about it and wait for staff, alternatively you could have just told him to stop shooting over as the rebel spawn border is right there, from their POV they could not see the rebel borders sign
When handling spawncamp situations (and for things in general), GMs are not required to switch to the Staff-On-Duty (SOD) whitelist.
It is heavily encouraged, and there are benefits to being on the SOD job which make it worthwhile to do so (Ex. being unable to get cuffed), but it is not a requirement.
That is all for now.
Ancient GRID CmD, prior SU Major/GB COL.
Credit to SEVIN.
Arguments regarding the punishment sheet notwithstanding, (as that is a separate issue) TK without a legitimate reason as explicitly defined in the rules or as set by precedent (it has been a long standing precedent that SU are allowed to kill captured rebels though it is not explicitly stated) is against the rules.
Being that it is common knowledge that the rules of the server trump factional rules, not to mention the stupidity of responding to rulebreaking via rulebreaking, rules of the faction aren’t an excuse as Oil said. By the way, there are no factional rules in the resistance that support tking people who break the rules so idk where you get off saying “both factional co teams support it” lol.
As far as what I’ve seen in this forum post, no one addressed the fact that you could have asked in team chat to stop spawncamping, or that you could have ran up to the individual recording this to tell him to stop or face a demotion (as you are in your power to do based on the relatively new combine demotion policy).
TKing spawn campers is not how you should deal with situations like these, you could either:
A: Tell them to stop
B: Call staff and let them deal with it from there
Even if you TKed to deal with a rulebreaker doesnt mean that you didnt just break a rule and that you wont be punished for it
we do not encourage players to deal with rule breakers by themselves, if you see someone breaking a rule you can make a ticket about it and wait for staff, alternatively you could have just told him to stop shooting over as the rebel spawn border is right there, from their POV they could not see the rebel borders sign
Thread Locked/Moved.