Denied Remove being able to hack out SCPs below 50 players.

This suggestion has been denied and will not receive development.
Status
Not open for further replies.
Aug 27, 2023
131
20
61
What does this suggestion change/add/remove:
It makes it so that people cant hack out SCPs below 50 players.

Has something similar been suggested before? If so, why is your suggestion different?:
I don't know but probably.

Possible Positives of the suggestion (At least 2):
-It would make the game playable at late night.
-Beneficial as the player count is very low at late night so it can make the game better for them as they can actually do stuff.
-Prevents early mass breaches.
-People who play late at night will not have to just focus on a breach for a good while.
-Less breaches.


Possible Negatives of the suggestion:
-N/A

Based on the Positives & Negatives, why should this suggestion be accepted:
I believe this should be accepted because D-Class hacking out SCPs late at night for example is just not fun and difficult to deal with late at night. The last 2 nights in a row this has happened. The first night D-Class 914'd and breached: 079, 035 x4 and 076, while still being disguised and killing people trying to RC the breach and even then only 2 people were on that could combat that breach. Last night, D-Class 914'd and split into 3 groups of two to breach SCPs, which they succeeded in two of them: 035 and TG but failed 079 and 7722, and killing people while disguised. Both these breaches took over an hour to RC. These are just two amazing examples of why this needs to be removed as this is difficult to deal with, unfun and disrupt any RP that is happening around that time. These breaches also create a great oppurtunity for D-Class to go back to 914 if they die as everyone is distracted by the breach.
 
Last edited:
can you sum this up in fortnite terms
"The text is a critique of recent changes in a roleplaying server (likely for SCP-related gameplay) where certain mechanics, like mass breaching SCPs, are being penalized, particularly during low population (lowpop) periods. The author argues that mass breaching is not explicitly against the rules and that staff are unfairly banning players for actions that were previously allowed. They criticize staff for enforcing rules that aren't written down or publicly announced, causing confusion among players. The author suggests that mass breaching should not be punishable unless it becomes repetitive or is done without intent to roleplay, especially when it harms server health. They also point out that the situation referenced in a ban appeal was more complex than simply mass breaching and involved ignoring staff warnings. Ultimately, the author advocates for more clarity in rules and fairer enforcement of them."

ChatGPT clutch
 
Dec 10, 2022
80
21
111
"The text is a ..."
AI slop actually did its job somewhat accurately for once.
This more seems like a complaint than a responce TBH, you just complained about bans for it.
Inherently the main complaint was that for some reason there's a major push to make the standard SCP server like Site 9 (nothing ever happens).
D-class roaming free and somehow getting access to keycards + hacking devices should be 'OH FUCK' not 'oh well we'll catch them at some point'.

Neutering the threat of antagonists (e.g SCPs, D-Class, CI, GOC rarely) is not healthy for the server I'd argue as a majority of the reason why people play SCP at the moment isn't for roleplay but rather the mechanical side of it.

I don't disagree with removing them, mind you, I just feel it's a slippery slope and a feature best reserved for Site 9 if it isn't done dirty like Starwars RP; if we're going to start nerfing the ability to breach SCP's even more, what stops SSL/NL from just declaring the current server Site 9 with a map switch (come back in a few years and tell me if I was right lmao); which would be a tragedy, frankly.

I don't know, it's just a strange trend people don't like talking about (how they're babifying the server because players cant behave).
 
-SUPPORT
WE ARE NOT SITE 9


Why are we removing yet another feature that made D-class escaping dangerous? First it was CL5's being nuked from 914 (no more funny infobreaches) and now people are wanting to remove hacking out SCPs on lowpop? (NOT ONLY THAT BUT THIS REMOVES THE ENTIRE POINT OF DOING EARLY MORNING DEEPCOVERS)

Yes, it is annoying.
No, that doesn't mean you should be trying to remove it.

Why are we punishing people for 'mass breaching on lowpop' with bans when it isn't even in the fucking rules?
Some CN staff are actually delusional at this point (you can get banned for something not written down and previously allowed, atop of the whole 079 incident as of recent)

The reason I say it's a delusion is because quite literally it's not written anywhere. Not in staff guidelines, not in player guidelines, not in SCPRP rulings, not in SCPRP rules. Where did this rule come from? Who authorised you to ban people for it?

JUST BECAUSE YOU DO NOT LIKE A MECHANIC DOES NOT MEAN USING IT CONSTITUTES A RULEBREAK.

Me when I spread misinformation online.

Mass Breaching SCPs has never and will never be against the rules, it was only bannable to do shit like breach 096/008 as doing so would usually also get you killed (and was literally against the rules to breach 096 by looking at his face then running away, or breaking into 008).

If you've seen staff warn people over this without very good reason, please make a staff complaint; they have no grounds to ban you for something like this without contacting actual SL as they can't make 'server health decisions' below that lmfao.

Sorry, where is this in rulings or rules? I know it can come off as insulting (the top half of this post), but I am genuinely curious where this misconception came from. If it is bannable, players should KNOW it is bannable, yes? By proxy - the fact it isn't in the rules anywhere I can find (and no announcements have been made about it); means that, currently.

You can be banned for something (according to your statement) you had NO IDEA was against the rules, and HAD no ability to even know it was against the rules.

This is what I mean by SCPRP going downhill and really fast. Staff are enforcing actually made up rules at this point (and not being called out for it, it seems).

I actually think it's important to clarify too - you will not be server health banned for just mass breaching over and over, that shit takes like, weeks of being an absolute menace to society to earn a server health ban (trust me I've tried prior as chef), like I've previously mentioned, usually that takes SL to go "Yeah fuck this guy in particular" and auth it; if that's changed since, so be it; but like I said.

There's no indication in the rules of this being the case, so whoever issued those bans might need to be retrained. (ignoring the one linked. Please, if you see other staff banning people for this shit without SL authing it, let SL know.)

Of course, I am also very aware of why the person which you are referencing was banned, and wasn't for mass breaching exclusively (as mentioned). The guy was literally mass breaching day after day, almost racking up failRP warns with some of the ways he was doing it/escaping, along with meta/etc(NITRP since they avoided testing, roleplay etc). There was a crazy amount of lore involving that situation and reducing it to "oh lmao if you mass breach you'll be banned" is a very bad oversimplification; considering he was banned for Server Health Reasons; but that wasn't exclusive to mass breaching.
For clarification - this is the thread that people love to cite.


In the thread itself it literally was said that they were banned for ignoring SL asking them to stop rather than the action itself, they were given a chance and told to 'chill out dude' since it was harming pop, and then when they refused, yeah, they were banned. This can happen with like, literally anything SL tells you not to do. (I also think it's important to note that in this case it was almost NITRP as the person in question literally didn't want to do anything, by their own admission, than 'play the core gameplay loop of D-class').

TLDR to most of the above;
It is not bannable to mass-breach in an isolated incident.
It is bannable to do it repeatedly, with no intent to roleplay, for the exclusive reason of 'muh gameplay' after SL tell you to stop.
Server Health is a very complex ban reason, simplifying it down to 'he mass breached and thus was server health banned' was a really bad example to set - especially considering the reason he ended up being banned is because SL told him to stop and he ignored them.


Mass Breaching is fine, if it happens rarely.
server health and roleplay quality first bud when theres no one actively roleplaying on low pop
 
Jan 6, 2023
466
157
111
24
"The text is a critique of recent changes in a roleplaying server (likely for SCP-related gameplay) where certain mechanics, like mass breaching SCPs, are being penalized, particularly during low population (lowpop) periods. The author argues that mass breaching is not explicitly against the rules and that staff are unfairly banning players for actions that were previously allowed. They criticize staff for enforcing rules that aren't written down or publicly announced, causing confusion among players. The author suggests that mass breaching should not be punishable unless it becomes repetitive or is done without intent to roleplay, especially when it harms server health. They also point out that the situation referenced in a ban appeal was more complex than simply mass breaching and involved ignoring staff warnings. Ultimately, the author advocates for more clarity in rules and fairer enforcement of them."

ChatGPT clutch
im not reading allat
 
  • Haha
Reactions: Niox
Jan 5, 2024
47
24
61
-SUPPORT
WE ARE NOT SITE 9


Why are we removing yet another feature that made D-class escaping dangerous? First it was CL5's being nuked from 914 (no more funny infobreaches) and now people are wanting to remove hacking out SCPs on lowpop? (NOT ONLY THAT BUT THIS REMOVES THE ENTIRE POINT OF DOING EARLY MORNING DEEPCOVERS)

Yes, it is annoying.
No, that doesn't mean you should be trying to remove it.

Why are we punishing people for 'mass breaching on lowpop' with bans when it isn't even in the fucking rules?
Some CN staff are actually delusional at this point (you can get banned for something not written down and previously allowed, atop of the whole 079 incident as of recent)

The reason I say it's a delusion is because quite literally it's not written anywhere. Not in staff guidelines, not in player guidelines, not in SCPRP rulings, not in SCPRP rules. Where did this rule come from? Who authorised you to ban people for it?

JUST BECAUSE YOU DO NOT LIKE A MECHANIC DOES NOT MEAN USING IT CONSTITUTES A RULEBREAK.

Me when I spread misinformation online.

Mass Breaching SCPs has never and will never be against the rules, it was only bannable to do shit like breach 096/008 as doing so would usually also get you killed (and was literally against the rules to breach 096 by looking at his face then running away, or breaking into 008).

If you've seen staff warn people over this without very good reason, please make a staff complaint; they have no grounds to ban you for something like this without contacting actual SL as they can't make 'server health decisions' below that lmfao.

Sorry, where is this in rulings or rules? I know it can come off as insulting (the top half of this post), but I am genuinely curious where this misconception came from. If it is bannable, players should KNOW it is bannable, yes? By proxy - the fact it isn't in the rules anywhere I can find (and no announcements have been made about it); means that, currently.

You can be banned for something (according to your statement) you had NO IDEA was against the rules, and HAD no ability to even know it was against the rules.

This is what I mean by SCPRP going downhill and really fast. Staff are enforcing actually made up rules at this point (and not being called out for it, it seems).

I actually think it's important to clarify too - you will not be server health banned for just mass breaching over and over, that shit takes like, weeks of being an absolute menace to society to earn a server health ban (trust me I've tried prior as chef), like I've previously mentioned, usually that takes SL to go "Yeah fuck this guy in particular" and auth it; if that's changed since, so be it; but like I said.

There's no indication in the rules of this being the case, so whoever issued those bans might need to be retrained. (ignoring the one linked. Please, if you see other staff banning people for this shit without SL authing it, let SL know.)

Of course, I am also very aware of why the person which you are referencing was banned, and wasn't for mass breaching exclusively (as mentioned). The guy was literally mass breaching day after day, almost racking up failRP warns with some of the ways he was doing it/escaping, along with meta/etc(NITRP since they avoided testing, roleplay etc). There was a crazy amount of lore involving that situation and reducing it to "oh lmao if you mass breach you'll be banned" is a very bad oversimplification; considering he was banned for Server Health Reasons; but that wasn't exclusive to mass breaching.
For clarification - this is the thread that people love to cite.


In the thread itself it literally was said that they were banned for ignoring SL asking them to stop rather than the action itself, they were given a chance and told to 'chill out dude' since it was harming pop, and then when they refused, yeah, they were banned. This can happen with like, literally anything SL tells you not to do. (I also think it's important to note that in this case it was almost NITRP as the person in question literally didn't want to do anything, by their own admission, than 'play the core gameplay loop of D-class').

TLDR to most of the above;
It is not bannable to mass-breach in an isolated incident.
It is bannable to do it repeatedly, with no intent to roleplay, for the exclusive reason of 'muh gameplay' after SL tell you to stop.
Server Health is a very complex ban reason, simplifying it down to 'he mass breached and thus was server health banned' was a really bad example to set - especially considering the reason he ended up being banned is because SL told him to stop and he ignored them.


Mass Breaching is fine, if it happens rarely.
Even in that case the reason for banning him should not be "server health reasons" and more "negation to RP" (whatever the rule is called)

Its a thin wall actually, if i play only Dclass and manage multiple times to escape and mass breach SCPs (while i was RPing like testing and stuff) SL should not come and say "Here dont do that" because its not in the rules, make a rule for it or just dont allow people to hack SCPs out during low pop.

When CI comes and breaches SCP over and over no SL comes and tell them to stop even if results in 1,5h long breaches
 

Holland

Head Moderator
Head Moderator
SCP-RP Staff
Content Team
Donator
Aug 27, 2022
289
37
111
Suggestion Denied



Hi @Cain_Morris14 ,

Thanks for taking the time to make a server suggestion.
The Content Team has chosen to deny your suggestion due to the following reasons.

Other plans are already in progress (WIP) for balancing breached SCPs and hacking SCPs during lower player counts.

Your suggestion will now be locked and marked as denied.​
 
Jul 5, 2022
436
89
111
-SUPPORT
WE ARE NOT SITE 9


Why are we removing yet another feature that made D-class escaping dangerous? First it was CL5's being nuked from 914 (no more funny infobreaches) and now people are wanting to remove hacking out SCPs on lowpop? (NOT ONLY THAT BUT THIS REMOVES THE ENTIRE POINT OF DOING EARLY MORNING DEEPCOVERS)

Yes, it is annoying.
No, that doesn't mean you should be trying to remove it.

Why are we punishing people for 'mass breaching on lowpop' with bans when it isn't even in the fucking rules?
Some CN staff are actually delusional at this point (you can get banned for something not written down and previously allowed, atop of the whole 079 incident as of recent)

The reason I say it's a delusion is because quite literally it's not written anywhere. Not in staff guidelines, not in player guidelines, not in SCPRP rulings, not in SCPRP rules. Where did this rule come from? Who authorised you to ban people for it?

JUST BECAUSE YOU DO NOT LIKE A MECHANIC DOES NOT MEAN USING IT CONSTITUTES A RULEBREAK.

Me when I spread misinformation online.

Mass Breaching SCPs has never and will never be against the rules, it was only bannable to do shit like breach 096/008 as doing so would usually also get you killed (and was literally against the rules to breach 096 by looking at his face then running away, or breaking into 008).

If you've seen staff warn people over this without very good reason, please make a staff complaint; they have no grounds to ban you for something like this without contacting actual SL as they can't make 'server health decisions' below that lmfao.

Sorry, where is this in rulings or rules? I know it can come off as insulting (the top half of this post), but I am genuinely curious where this misconception came from. If it is bannable, players should KNOW it is bannable, yes? By proxy - the fact it isn't in the rules anywhere I can find (and no announcements have been made about it); means that, currently.

You can be banned for something (according to your statement) you had NO IDEA was against the rules, and HAD no ability to even know it was against the rules.

This is what I mean by SCPRP going downhill and really fast. Staff are enforcing actually made up rules at this point (and not being called out for it, it seems).

I actually think it's important to clarify too - you will not be server health banned for just mass breaching over and over, that shit takes like, weeks of being an absolute menace to society to earn a server health ban (trust me I've tried prior as chef), like I've previously mentioned, usually that takes SL to go "Yeah fuck this guy in particular" and auth it; if that's changed since, so be it; but like I said.

There's no indication in the rules of this being the case, so whoever issued those bans might need to be retrained. (ignoring the one linked. Please, if you see other staff banning people for this shit without SL authing it, let SL know.)

Of course, I am also very aware of why the person which you are referencing was banned, and wasn't for mass breaching exclusively (as mentioned). The guy was literally mass breaching day after day, almost racking up failRP warns with some of the ways he was doing it/escaping, along with meta/etc(NITRP since they avoided testing, roleplay etc). There was a crazy amount of lore involving that situation and reducing it to "oh lmao if you mass breach you'll be banned" is a very bad oversimplification; considering he was banned for Server Health Reasons; but that wasn't exclusive to mass breaching.
For clarification - this is the thread that people love to cite.


In the thread itself it literally was said that they were banned for ignoring SL asking them to stop rather than the action itself, they were given a chance and told to 'chill out dude' since it was harming pop, and then when they refused, yeah, they were banned. This can happen with like, literally anything SL tells you not to do. (I also think it's important to note that in this case it was almost NITRP as the person in question literally didn't want to do anything, by their own admission, than 'play the core gameplay loop of D-class').

TLDR to most of the above;
It is not bannable to mass-breach in an isolated incident.
It is bannable to do it repeatedly, with no intent to roleplay, for the exclusive reason of 'muh gameplay' after SL tell you to stop.
Server Health is a very complex ban reason, simplifying it down to 'he mass breached and thus was server health banned' was a really bad example to set - especially considering the reason he ended up being banned is because SL told him to stop and he ignored them.


Mass Breaching is fine, if it happens rarely.
holy YAP stop complaining lmao maybe just like idk dont fuck up server health during low pop making the server unplayable?
 
Jul 5, 2022
436
89
111
Suggestion Denied



Hi @Cain_Morris14 ,

Thanks for taking the time to make a server suggestion.
The Content Team has chosen to deny your suggestion due to the following reasons.

Other plans are already in progress (WIP) for balancing breached SCPs and hacking SCPs during lower player counts.

Your suggestion will now be locked and marked as denied.​
why is resource team replying to this
 
  • Haha
Reactions: Niox
Status
Not open for further replies.