SCP-073 and the Effect of Allowing the Populace to play an Extremely Complex SCP.

notcain

notcain

Civil Gamers Expert
One Year Club
May 5, 2024
5
1
61
What does this suggestion change/add/remove:

- This SCP will add in a whitelist for SCP-073 while giving him his ability to reflect back. Currently SCP-073 feels awful to play because of people viewing him as a nuisance due to previous players using him to support/help SCPs (which is out of characters) or somehow be a detriment to the Foundation. With the whitelist, people could begin to trust SCP-073 players and actually view them as he is in lore.
- Requirements for the whitelist: 20 in Support and Research, 10 in SCP, 80 in total.

- With the increased respect from the whitelist, he should also allow him to pick up items. Why? So, he can actually assist around site and do menial tasks that more busy people can't do as that's how he's described in Resurrection and other canons. Prevent him from picking up any weapon to retain his non-combatant status. He already has the ability to turn documents and clipboards into ash (gets XP for doing this), so adding his secondary anomaly shouldn't be needed.

- SCP-073 should also be able to receive a reskin of the clipboard as he is stated as something of a writer, with it he would be able to upload documents and print stuff.

Has something similar been suggested before? If so, why is your suggestion different?:

Yes, it has a year ago, but was denied. I could not find a reason, but I assume that it's because if the content team had to work on SCP-073 it would take away from other stuff for a SCP that will be less played. Well, nothing has changed, but SCP-073 is still horrendous to play, driving others away. If he was added properly and not half baked like he is right now, I believe that he would see more players.

Possible Positives of the suggestion (At least 2):

- Better player quality of SCP-073 players.
- Gives SCP-073 more opportunities to involve himself in the roleplay.
- Allows SCP-073 to actually be a productive member of the Foundation/Server.
- Return some respect to SCP-073 player's.

Possible Negatives of the suggestion:

- Changes for a SCP that might not be impactful if no one plays SCP-073.
- SCP-073 being able to pick up stuff could open the role to bugs and exploits.
- Increased moderation by server leadership as it's another whitelist that they'll have to manage.

Based on the Positives & Negatives, why should this suggestion be accepted:

Based on the positives and negatives, SCP-073 should be changed massively to better fit his lore, add more RP SCPs, and allow him to be more flexible. SCP-073 will still retain his SCP designation, having no real authority like his currently. Outside of being able to pick up items, this would be an easy suggestion to add to better the SCP that has been tortured with nerfs.
 
Upvote 2 Downvote
stone. said:
huh this is talking about 073
Click to expand...
Oop, I somehow misread the 3 as a 9. Reading closer, it makes more sense now. I was going to ask when 079 had any kind of reflect capability 🤪

In which case -
Ronin said:
" We can't trust the playerbase with this cool thing so we are gonna make it so that no one can interact with this cool thing. " 🤓
Click to expand...
Honestly... We literally can't. 073's damage reflection was taken away because people abused it. Then 073's collision was taken away because people abused it. And each time we suggest improvements and direction for 073 development, they get denied with sentiments along the lines of "This isn't necessary, 073 is fine as it is" or "This is not something we want to focus on." So we had this aimless role that had things it could do, but no direction with which to positively contribute them - Which led to minging. And to my knowledge, people still find ways to minge on 073, which adversely affects anyone that wants to genuinely play the role because the minging has led to the now deeply rooted assumption that minging on 073 is the norm, which ironically, makes less people want to play 073 normally, leaving only minges - Further reinforcing it.

Honestly at this point, I'd advocate for a temporary removal of 073 as a flaggable role until such a time when there is a need to bring it back with renewed interest. Which is a difficult decision, given the recent addition of a CC for it, but in even its current, nerfed state, it's too destructive and causes too many headaches, with few ways of dealing with it outside of Staff intervention.

Alternatively, if we can't do that, then just make it a minge lightning rod - Maximise its capability to minge while also increasing the ways that abuse can be punished. Make 073 attackable by other SCPs and reimplement the "bug" where it could become an 096 target, but 096 mutually dies when it tries to kill 073. Give it a gun and exemptions from RDM rules. Just go completely nuts.

The intention for what 073 should be has not been met - And when we raise it, IMO we just always get these milquetoast responses and/or actions that feel unsatisfactory. I get that this is difficult. What I don't understand is why the constant soft attitude towards 073? The fact of the matter is, 073 has a cemented reputation as (one of) the minge job(s). And if there are no plans to change that for the better in the foreseeable future, then shelf the role entirely. Just take 073 away., doesn't have to be forever.
 
Emilia Foddg said:
Oop, I somehow misread the 3 as a 9. Reading closer, it makes more sense now. I was going to ask when 079 had any kind of reflect capability 🤪

In which case -

Honestly... We literally can't. 073's damage reflection was taken away because people abused it. Then 073's collision was taken away because people abused it. And each time we suggest improvements and direction for 073 development, they get denied with sentiments along the lines of "This isn't necessary, 073 is fine as it is" or "This is not something we want to focus on." So we had this aimless role that had things it could do, but no direction with which to positively contribute them - Which led to minging. And to my knowledge, people still find ways to minge on 073, which adversely affects anyone that wants to genuinely play the role because the minging has led to the now deeply rooted assumption that minging on 073 is the norm, which ironically, makes less people want to play 073 normally, leaving only minges - Further reinforcing it.

Honestly at this point, I'd advocate for a temporary removal of 073 as a flaggable role until such a time when there is a need to bring it back with renewed interest. Which is a difficult decision, given the recent addition of a CC for it, but in even its current, nerfed state, it's too destructive and causes too many headaches, with few ways of dealing with it outside of Staff intervention.

Alternatively, if we can't do that, then just make it a minge lightning rod - Maximise its capability to minge while also increasing the ways that abuse can be punished. Make 073 attackable by other SCPs and reimplement the "bug" where it could become an 096 target, but 096 mutually dies when it tries to kill 073. Give it a gun and exemptions from RDM rules. Just go completely nuts.

The intention for what 073 should be has not been met - And when we raise it, IMO we just always get these milquetoast responses and/or actions that feel unsatisfactory. I get that this is difficult. What I don't understand is why the constant soft attitude towards 073? The fact of the matter is, 073 has a cemented reputation as (one of) the minge job(s). And if there are no plans to change that for the better in the foreseeable future, then shelf the role entirely. Just take 073 away., doesn't have to be forever.
Click to expand...
Aware.

Hence the extra stipulations. I believe SCP-073 can work, but if the development team won't try anything. I would be fine with him being removed, SCP-073 has so much potential, but is hard gimped by other people playing him badly? And it's not like staff does anything to mediate this. Though, you could say this for all of the roaming SCPs besides 912 as they all have keycards. I've seen more people release D-Class on 2295 and 999 just by the matter of them being more popular. I would also be fine with all of the roaming SCPs being whitelisted. This isn't really a SCP-073 issue, but also an issue for the servers as a whole.

I also think a clipboard reskin and the ability to pick stuff up would really advance what 073 could do instead of being a spectator. SCP-073's cell is magnificent, but uh. I don't think we should be adding more friendly/roaming SCPs until they find a fix for the minging problem because people could get a few levels on SCP before opening all the doors and letting all the SCPs in.

It's hard to imagine the others as whitelisted too, but unfortunately the community will ruin a good thing in exchange for gameplay satisfaction.
 
Emilia Foddg said:
Honestly... We literally can't. 073's damage reflection was taken away because people abused it. Then 073's collision was taken away because people abused it. And each time we suggest improvements and direction for 073 development, they get denied with sentiments along the lines of "This isn't necessary, 073 is fine as it is" or "This is not something we want to focus on." So we had this aimless role that had things it could do, but no direction with which to positively contribute them - Which led to minging. And to my knowledge, people still find ways to minge on 073, which adversely affects anyone that wants to genuinely play the role because the minging has led to the now deeply rooted assumption that minging on 073 is the norm, which ironically, makes less people want to play 073 normally, leaving only minges - Further reinforcing it.
Click to expand...
Honestly. I think making it a whitelisted role would solve alot of this.
90% of the time a minge isn't gonna put the work into writing a substantial or well thought out application to a SCP whitelist, they'll just do like the rest and play 2295, 999, or 912.
Emilia Foddg said:
Honestly at this point, I'd advocate for a temporary removal of 073 as a flaggable role until such a time when there is a need to bring it back with renewed interest. Which is a difficult decision, given the recent addition of a CC for it, but in even its current, nerfed state, it's too destructive and causes too many headaches, with few ways of dealing with it outside of Staff intervention.
Click to expand...
This would be solved by whitelisted role as well. Kinda like a next step from executive.
Emilia Foddg said:
Alternatively, if we can't do that, then just make it a minge lightning rod - Maximise its capability to minge while also increasing the ways that abuse can be punished. Make 073 attackable by other SCPs and reimplement the "bug" where it could become an 096 target, but 096 mutually dies when it tries to kill 073. Give it a gun and exemptions from RDM rules. Just go completely nuts.
Click to expand...
Weird direction tbh, completely unexpected direction. I disagree this being a solution as I see the high potential in 073 being used as a "super researcher" one able to go into a CC and interact with SCPs directly in RP senerios. But the issue is it's a cl2 and accessible by anyone, so respected as a researcher by none. Hell I don't even know if it can credit anyone.
Emilia Foddg said:
The intention for what 073 should be has not been met - And when we raise it, IMO we just always get these milquetoast responses and/or actions that feel unsatisfactory. I get that this is difficult. What I don't understand is why the constant soft attitude towards 073? The fact of the matter is, 073 has a cemented reputation as (one of) the minge job(s). And if there are no plans to change that for the better in the foreseeable future, then shelf the role entirely. Just take 073 away., doesn't have to be forever.
Click to expand...
Honestly this I agree with. There's too many SCP that just serve no purpose beyond breaching, or minging. 073 is the biggest wasted potential in this server second only to medical.
 
I mean, 22415 is whitelisted, and the minge potential for 22415 is incredibly rarely used, same situation here maybe.

+support
 
You must log in or register to reply here.
Top Bottom
Back