Asking for a scp to hop on with the sole intent to breach it shouldn't be a thing, work with your timing and whatever scps are on-site.
[...]
we are asking for rules to be added so SCP's aren't flagged on with the sole intent of breaching
Does this include D-Class?
The main argument that CI have always tried to use whenever someone has argued this before is the staff ruling regarding SCPs that they are "always onsite IC" and thus its fair to ask any singular SCP on to breach them. For starters, is that argument not paradoxical itself? If the SCPs are always on at all times, and yet CI continuously only flag onto SPECIFIC SCPs that they know provide them the best benefit to their raid even if others are not available, is that not also just metagame from them knowing what SCPs are available by essentially looking at the scoreboard just to ensure maximum raid success with no variety whatsoever?
You make a compelling argument. ...I agree that this specific issue is a problem and even if something were done about the scoreboard, you could always just find out from the SCP tab anyway.
The argument literally goes both ways when you think about it like this and it makes you think that it's genuinely more hassle than it's worth to allow them to keep doing this, because god knows how long I've seen people beg for this.
I'm an F main, but have played a decent amount of CI and I often see sentiment held in both along the lines of the other side being largely uninterested in RP and just wanting combat. Conversely, I've seen good RP come from F & CI both.
People are likely begging for it because they seem to be under the impression that CI always metagame despite probably only occasionally having the full picture. And as a result, developing the mentality that when CI raid, they will always plant people on SCP roles to have them team, despite this being explicitly disallowed.
Secondly, the argument that CI Command enforce these rules in order to ensure they don't ruin role-play is hilariously rich
...It shouldn't be, because it's a matter of server rules. This reads more as difficulty of enforcement being misconstrued as it being permitted.
I had to make a complaint that two members of CI REGCOM+ were sitting in the CI TS on SCPs that made it to surface, JUST as conveniently, a main gate slaughter of a CI raid appeared! The winning mentality behind all of the logic involved is utterly ridiculous.
So just as an engineered encounter should be rightfully penalised, what exactly happens during coincidence? And how do you tell the two apart? While I don't disagree that this happens at all or that it should be curbed, this is starting to sound less like an issue with CI and more like a conspiracy. You can't seriously expect me to believe that this is happening with such frequency and always with always such intention behind it.
I'll tell you the same thing that Staff probably might regarding this - If there's issues hold onto evidence, call sits, raise it with SL, make complaints, etc. Making a new rule out of this is either:
- Not going to work, at least in the way you seem to see it working
- Be circumvented by bad actors who were likely already breaking the rules anyway
- Be near-impossible to enforce or at the very least, a massive headache for Staff to do so effectively because of the arbitrary nature of it
Or all/any mix of the above.
You have OTHER ways to cause chaos within the Foundation. Pairing two of the main combat loops that on their own are already designed to disrupt Foundation function together, just so that you can get the dopamine of a longer raid and thus a higher K/D, is irrelevant. I know SSL+ are working hard on trying to find more things to do on the surface for you, hell I know for a fact I wouldn't mind a CL5 meeting to also share ideas. But I'm at the end of my tether again with single breaches like 035 managing to somehow snowball consistently into a nuke.
I'm all for you using role-play to do this, if you actually did. For example, if an SCP was ALREADY flagged on such as 7722, stayed on long enough for a DC to find them first and confirm presence, THEN CI raided and breached it. I genuinely would have no ground to stand on, cause that would at least require setup, have counterplay and engage people. The current loop is literally just "kill people near the SCPs likely to give us the best K/D, then issue the flag on, finish the hack and boom, roleplay is ruined.
Honestly, a fun IC plot beat could be to allow CI sample SCPs ala GOC (albeit a bit more strictly controlled) in place of a raid. It sounds insane, but you could reasonably ICly contextualise this somehow.
Plus it would just be extremely funny, imagine allowing CI to sample an SCP.
Ultimately, I do agree that there is a problem with breach severity. I just don't believe the proposed solution is reasonably enforceable. Are you intending on having anyone flagging on an SCP during a raid be actioned against and if they're found to hold a CI rank, force flagged off? What's the angle here?
Game Master
Donator
Trial Moderator
SCP-RP Staff
Event Team
