General suggestion - Calling AOS/KOS on branches - Denied

[Average Pipebomb enjoyer]

What are you suggesting? - A rule so you cant call a KOS/AOS on a entire branch and actually have to have a name to call a AOS/KOS On a person

How would this change better the server? - It would add a bit of realism and it would prevent people from just saying ''i was attacked by a (Insert branch) lets call a KOS on said branch'' and after killing the sleuth just calling off the KOS order

Are there any disadvantages of making this change to the server? If so, explain. - it would be a bit of a disadvantage towards foundation branches

Who would this change mostly benefit? -  Sleuths

Please link any workshop content, screenshots, or anything that you think may be helpful to those who view this suggestion - N/A

[Chief_]

+/-Support

+It would be nice to have it clarrified that you can't call kos/aos on an entire branch without a valid reason. 

Like KOS all of gensec for rebelling because they want better wages, researchers for going rogue. 

+/-It is already kindoff failrp to jsut call a KOS/AOS on an entire branch just off of one person. 

 

But tell me if you mean this for that when we see something suspicious. Like a researcher roaming with CI that we can't have a "Check all researchers Id's". Because if so then full -support. You just have to play it more safe and not get caught. 

[Average Pipebomb enjoyer]

i dont think you should be able to KOS the entirety of research in a certain area because 1 person got caught in a research uniform and get away with it by saying ''i didnt catch their name so KOS research in HCZ'' 

1 hour ago, Chief_ said:

You just have to play it more safe and not get caught. 

 

Edited June 6, 2021 by russianweeb69

[[Triggred]Perisnot]

+/- support 

+ to calling AOS if a certain sleuth of a disguised branch kills a redacted member, but I do not think it should be KOS, they should just AOS them and check everyone's identity.

- to the KOS order, would be too much RDM, unless there was like an RP reset once everyone finished their NLR

[Chief_]

21 minutes ago, russianweeb69 said:

i dont think you should be able to KOS the entirety of research in a certain area because 1 person got caught in a research uniform and get away with it by saying ''i didnt catch their name so KOS research in HCZ'' 

 

I agree with the kos prt. But if your saying to dissalow id checks then I say -support. They shouldn’t do that. 

[Average Pipebomb enjoyer]

4 minutes ago, Chief_ said:

But if your saying to dissalow id checks

i want it to be ID checks instead of KOSing an entire branch ID checks should be allowed and encouraged 

14 minutes ago, [Triggred]Perisnot said:

to the KOS order, would be too much RDM,

KOS orders on entire branches should NOT be allowed 

[Chief_]

6 minutes ago, russianweeb69 said:

i want it to be ID checks instead of KOSing an entire branch ID checks should be allowed and encouraged 

KOS orders on entire branches should NOT be allowed 

Then I give a full +support. It should never be kosing. 

[Southpaw]

The only people able to call an KOS/AOS on a full branch would be (I think, correct me if im wrong) SA, O5, and (I think I'm wrong) SF?

They shouldnt be calling a full AOS/KOS on a branch because of a sleuth, if they do, report it to command.

+Support

[Guinea Pig]

+ Support 

only SA of that branch should be allowed and maybe high ranking SF, but even then people shouldn’t be doing this

[The Real Slim Nova]

22 hours ago, [Triggred]Perisnot said:

+/- support 

+ to calling AOS if a certain sleuth of a disguised branch kills a redacted member, but I do not think it should be KOS, they should just AOS them and check everyone's identity.

- to the KOS order, would be too much RDM, unless there was like an RP reset once everyone finished their NLR

Agree with this.

[Sixx]

+Support

People calling a KOS on an entire branch leads to multiple problems and sometimes hurts branch relations. This should be a thing left to Ethics and O5.

[recon]

On 6/6/2021 at 12:14 AM, Guinea Pig said:

+ Support 

only SA of that branch should be allowed and maybe high ranking SF, but even then people shouldn’t be doing this

 

[a frog]

-support

I for one am in support of weeding out a entire branch for what they did (look at when nu7 killed 8 rrh because wanted stepped into a level 5 room and d4 called a kill code on them)  sometimes people need other people to keep them in check and thats where the knowing your place comes in hand d4 and other people that can call mass kos's keep the other branches in check so one doesnt do something very stupid like killing all of the level 5 researchers and engineers in that room (btw d4 kill codes arent going away)

Edited June 7, 2021 by frog

[Average Pipebomb enjoyer]

6 hours ago, frog said:

(btw d4 kill codes arent going away)

See i think only SA+ or high ranking SF should be able to call KOS orders on entire branches

Edited June 7, 2021 by russianweeb69

[Cloaker]

6 hours ago, frog said:

-support

I for one am in support of weeding out a entire branch for what they did (look at when nu7 killed 8 rrh because wanted stepped into a level 5 room and d4 called a kill code on them)  sometimes people need other people to keep them in check and thats where the knowing your place comes in hand d4 and other people that can call mass kos's keep the other branches in check so one doesnt do something very stupid like killing all of the level 5 researchers and engineers in that room (btw d4 kill codes arent going away)

Frog I see where you're coming from with this, I am in support of this suggestion but only to a limit. I don't think that you should lose the ability to order an entire branch to be killed, but as a sleuth I have had the KOS of an entire branch be ordered by RRH twice now. RRH is abusing this ability to kill sleuths, it doesn't make since that a kill order is called on an entire branch because of a sleuth?

Edited June 7, 2021 by Cloaker

[a frog]

20 hours ago, Cloaker said:

Frog I see where you're coming from with this, I am in support of this suggestion but only to a limit. I don't think that you should lose the ability to order an entire branch to be killed, but as a sleuth I have had the KOS of an entire branch be ordered by RRH twice now. RRH is abusing this ability to kill sleuths, it doesn't make since that a kill order is called on an entire branch because of a sleuth?

yes i do agree that if you call a kos on a entire branch for one sleuth that it is a mega waste and also sucks for the sleuth since they barley get to rp as is so i agree with you there. And if you feel that they are abusing it please go to the o5 about it since we dont need people calling them to much because it is in fact a abuse of power and fail rp to call a entire branch kos for one guy

[Rektify]

On 6/5/2021 at 8:42 PM, Southpaw said:

The only people able to call an KOS/AOS on a full branch would be (I think, correct me if im wrong) SA, O5, and (I think I'm wrong) SF?

They shouldnt be calling a full AOS/KOS on a branch because of a sleuth, if they do, report it to command.

+Support

 

21 hours ago, russianweeb69 said:

See i think only SA+ or high ranking SF should be able to call KOS orders on entire branches

I would +Support this. Only Site Administration would be allowed to call a KOS order on the branches. 

[Mav]

I disagree personally, I believe calling a KOS on a whole branch is fine as long as it's a valid reason like a mass info breach and they manage to get gas masks on.  But calling it because of one sleuth is ridiculous and is not allowed, if that happens you need to send proof to either me or the overseers of RRH.  I'm gonna say -Support though, mostly because they are SF and should be allowed to with a valid reason

Zulu 1 ~

{This is mostly for the foundation SF side if you couldn't tell.} 

Edited June 10, 2021 by Mav

[Average Pipebomb enjoyer]

16 hours ago, Mav said:

mostly because they are SF and should be allowed to with a valid reason

anyone can call a KOS on a branch and i dont think that should be allowed like i have no problem with high ranking SF calling KOS orders on branches with a valid reason

[Mind Stone]

1 hour ago, russianweeb69 said:

anyone can call a KOS on a branch and i dont think that should be allowed

I don't think this is correct. If however it is, this needs to be changed.

[Rookieblue]

There needs to be a valid RP reason for an AOS/KOS to be called. Making such a call on an entire branch would require a very significant reason, and would need to be done by someone that has authority over the branch, which would be at the Site Admin+ level. A specific MOTD change isn't required in my eyes, as it falls under the RP reason doctrine.

[Rangiatea]

On 6/12/2021 at 7:06 AM, Rookieblue said:

There needs to be a valid RP reason for an AOS/KOS to be called. Making such a call on an entire branch would require a very significant reason, and would need to be done by someone that has authority over the branch, which would be at the Site Admin+ level. A specific MOTD change isn't required in my eyes, as it falls under the RP reason doctrine.

 

[Rangiatea]

Denied. The SCP-RP SMT has decided against adding this suggestion for performance reasons, the benefit to the server, or another unstated reason.