Donator
What does this suggestion change/add/remove:
Add a location in Pinewood to the 096 picture spawn pool.Has something similar been suggested before? If so, why is your suggestion different?:
This is a direct re-opening of a suggestion on the same topic from 2 years ago. I think the circumstances between then and now are different enough that the server can reasonably support this because of the way things work now - And I think it's worth discussing again, especially since there are numerous relevant factors that are different between then and now, such as rules and the way the server works in general. More on this in the last section.Possible Positives of the suggestion (At least 2):
- + More reason to hack 096's containment box/breach tool it as opposed to just breaking all the doors to break it out (More on this in the last section)
- + Potentially less disruptive breaches (Yes, counterintuitive, more on this in the last section)
- + More worthwhile breaches for 096
- + Nu7, CI, GOC & MC&D will see more action
- + May create more RP for DEA, whether they like it or not
Possible Negatives of the suggestion:
- - Civilians may keep looking at 096 after respawning and cause it to keep rebreaching
- - Technically a CI buff
- - Potential issues w/ ERT if 096 stays uncontained too long and triggers auto-ERT
Based on the Positives & Negatives, why should this suggestion be accepted:
Haha, surprise, it's yet another 096 suggestion. Yes, I'm still mad about the bucket.Generally when people breach 096, if they have the option to hack it out (Or in the case of SCPs that can't hack it out, use a breach tool) or simply pull it from its CC, they will pull it from its CC. This is sort of a neutral thing because 096 being breached via breaking its doors means that even though it doesn't count as a breached SCP for further breaches, it always ends up breached within the site and ends up as varying levels of recontained easily or recontained after some level of disruption (Or on US, stuck under stairwell for 20 years if even 912 is also breached, because god why is this still allowed this is insane please make it stop make the voices stop aaaaaaaaa they'reinmywallsthey'reinmywalls).
Hacking the pic out is usually never considered because not only does that count towards a breach(?), but also there's situations where the pic can be somewhere no-one can see it, or it gets found and destroyed before anyone sees it (especially if it's face down), or 096 gets bucketed before it's able to get anywhere and the pic is destroyed that way, limiting the scope of the breach through no fault of the player. If there's the chance that it can spawn in Pinewood, it becomes a gamble whether you basically guarantee that 096 gets out and stays out for an extended period of time.
And it can end up less disruptive overall because when 096 has targets somewhere, you have to let 096 get to the targets. The only way to stop it is to use dimensions - Which is different from fighting other SCPs, because you are directly resisting them, because you can and should in fact stop them. The big concern with 096 is where it ends up after the fact. If that's somewhere in the site, then with that and another breach out, you have to handle both those things at the same time - However, Surface is a different story. If you know 096 is going to Surface, then you can just let that situation resolve itself. That's effectively one less breach to worry about, because you can't really stop anything. Granted, you still have to deal with where 096 ends up after the fact, however this is not potentially amidst another SCP breach.
Think of it this way:
096 and TG breach - Either by a pic spawning somewhere in the site or by TG breaking 096 out. TG can benefit from 096 by using it as a sort of 'push the payload' style objective and use 096 to defensively be stronger. And if it was by breaking 096 out, which is the most common method, this can end up being with ANOTHER SCP or even if solo TG, it still allows another breached SCP to be breached because 096 doesn't count as breached in this state.
Now imagine 096 and TG breaching again, but in this instance, 096 being breached is via someone seeing a picture spawned in Pinewood. 096 is OUT OF THERE. Neither TG nor anyone else can benefit from what I say above, because 096 is G O N E - This makes it easier to RC TG and potentially anything else that breached, too. Meanwhile, it's still beneficial to them somewhat because of the slight distraction of 096 tearing through the facility to get up to Surface - It's not like Foundation just completely ignore 096, so there's still something that the TG could benefit from, just not as much - Which is why from an SCP perspective that attempting to spawn the picture could be viable.
When it comes to RCing, both servers IMO are pretty good at handling 096 breaches to the point where I think that in the majority of cases when 096 reaches Surface as a result of this change, it would be bucketed long beforehand. This typically leads to capture by a Surface GOI, which I'm personally fine with, and would also be less disruptive than a roaming, unbucketed 096 on Surface, which is still possible but to my observation, far less likely. This is just simply a good change, IMO.
It seems unintuitive, but this is actually a general SCP nerf, all things considered. Give the situation some thought and see if you don't come to the same conclusion. This change can only be beneficial - And while I agree with why it was denied before, everything that's changed since then leads me to crunch everything I elaborate before - Which in turn strongly convinces me that the 096 picture should be able to spawn in Pinewood. Everyone wins.
Haha, surprise, it's yet another 096 suggestion. Yes, I'm still mad about the bucket.
Generally when people breach 096, if they have the option to hack it out (Or in the case of SCPs that can't hack it out, use a breach tool) or simply pull it from its CC, they will pull it from its CC. This is sort of a neutral thing because 096 being breached via breaking its doors means that even though it doesn't count as a breached SCP for further breaches, it always ends up breached within the site and ends up as varying levels of recontained easily or recontained after some level of disruption (Or on US, stuck under stairwell for 20 years if even 912 is also breached, because god why is this still allowed this is insane please make it stop make the voices stop aaaaaaaaa they'reinmywallsthey'reinmywalls).
Hacking the pic out is usually never considered because not only does that count towards a breach(?), but also there's situations where the pic can be somewhere no-one can see it, or it gets found and destroyed before anyone sees it (especially if it's face down), or 096 gets bucketed before it's able to get anywhere and the pic is destroyed that way, limiting the scope of the breach through no fault of the player. If there's the chance that it can spawn in Pinewood, it becomes a gamble whether you basically guarantee that 096 gets out and stays out for an extended period of time.
And it can end up less disruptive overall because when 096 has targets somewhere, you have to let 096 get to the targets. The only way to stop it is to use dimensions - Which is different from fighting other SCPs, because you are directly resisting them, because you can and should in fact stop them. The big concern with 096 is where it ends up after the fact. If that's somewhere in the site, then with that and another breach out, you have to handle both those things at the same time - However, Surface is a different story. If you know 096 is going to Surface, then you can just let that situation resolve itself. That's effectively one less breach to worry about, because you can't really stop anything. Granted, you still have to deal with where 096 ends up after the fact, however this is not potentially amidst another SCP breach.
Think of it this way:
096 and TG breach - Either by a pic spawning somewhere in the site or by TG breaking 096 out. TG can benefit from 096 by using it as a sort of 'push the payload' style objective and use 096 to defensively be stronger. And if it was by breaking 096 out, which is the most common method, this can end up being with ANOTHER SCP or even if solo TG, it still allows another breached SCP to be breached because 096 doesn't count as breached in this state.
Now imagine 096 and TG breaching again, but in this instance, 096 being breached is via someone seeing a picture spawned in Pinewood. 096 is OUT OF THERE. Neither TG nor anyone else can benefit from what I say above, because 096 is G O N E - This makes it easier to RC TG and potentially anything else that breached, too. Meanwhile, it's still beneficial to them somewhat because of the slight distraction of 096 tearing through the facility to get up to Surface - It's not like Foundation just completely ignore 096, so there's still something that the TG could benefit from, just not as much - Which is why from an SCP perspective that attempting to spawn the picture could be viable.
When it comes to RCing, both servers IMO are pretty good at handling 096 breaches to the point where I think that in the majority of cases when 096 reaches Surface as a result of this change, it would be bucketed long beforehand. This typically leads to capture by a Surface GOI, which I'm personally fine with, and would also be less disruptive than a roaming, unbucketed 096 on Surface, which is still possible but to my observation, far less likely. This is just simply a good change, IMO.
It seems unintuitive, but this is actually a general SCP nerf, all things considered. Give the situation some thought and see if you don't come to the same conclusion. This change can only be beneficial - And while I agree with why it was denied before, everything that's changed since then leads me to crunch everything I elaborate before - Which in turn strongly convinces me that the 096 picture should be able to spawn in Pinewood. Everyone wins.
This section was duplicated on purpose so that it could be ignored twice.
Last edited:
), and those could be used to pay for 096 instead of paying out of pocket.