Donator
What does this suggestion change/add/remove:
Give 860-2 breach behaviour - The same as most other breaching SCPs where if you hack its containment box, use a breach tool or it pops in the breach queue, then its containment blocker lifts and it is allowed out of its environment and CC, into the site. Even though it's kind of like an animal(?), I think it should be able to passive breach if it does not display hostility - Although I can understand there being issues with this, especially since I don't think it can talk. That's something to hash out down the line, but my prior experience as an E-11 CPT tells me that it'd make sense to not allow passive breaching of 860, as it'd be both difficult to work out and too risky to give it that kind of leeway.There would need to be decisions made about whether 860-2 is a non-terminable or terminable SCP and how much health it would have, its terminability being contextualised in RP as something like "What 860-2 is, is just one instance of an animal species native to the 860 dimension, so there's basically an infinite number of them in the 860 dimension." I would heavily recommend making it terminable to avoid any potential recontainment complications, but the final decision is up to you.
Accompanying these changes, similar other changes made in the past such as 912 being able to speak, there should be an event or a series of events (as in GM events) that justify 860-2's breach behaviour on the server sufficiently enough to make it make sense that 860-2 can now breach, basically boiling down to some reasoning like "the 860 dimension itself wanting to be interacted with" and because it is not interacted with that often by RsD, it "gets agitated(?)" and "it influences the forest's guardian (860-2) to exit the dimension into baseline reality for the express purpose of drawing attention to it." Or something along those lines. And it would be treated as "860-2 wasn't something that does this before, but is now. Why does it do this?" kind of situation, that could create long-term RP for RsD in investigating this new behaviour.
Has something similar been suggested before? If so, why is your suggestion different?:
This is a direct re-opening of my previous suggestion on the same topic. The only difference between then and now is that after a year, numerous factors have changed and I believe it worthwhile to re-open this discussion. I also particularly dislike the given denial reason and why I understand why you may not want to work on this, I feel that that denial reason largely ignored my specific reasoning and justification in terms of it making sense for 860 to breach (If that somehow wasn't clear). More in the final section.Possible Positives of the suggestion (At least 2):
- + More use of and spotlight on, 860 - It's a largely underutilised SCP that really only gets sampled because it has useful NVG chems. It could stand to be a lot more interesting and not just among the things that take up space, both on the map and in filesize.
- + Another breach option for players that want to breach as SCPs & players that want to hack out SCPs, using something already present in-game and practically almost complete - Although this may need adjustments to level requirements for 860 and such, unsure. I appreciate that not every SCP there is, nor every player SCP needs to also be able to breach, but I think there is wasted potential in not allowing 860 to breach.
- + Recontainment Difficulty Dilution - This is a concept I raise in the prior suggestion, but I think is more important now; Basically, if you introduce more breaches that are easier to contain, then the average difficulty to recontain a breach goes down, on the assumption that that new breach happens often enough to make a difference. Essentially, this may have a positive impact on roleplay by virtue of potentially making breaches shorter, by virtue of being an easier thing to contain when breached alongside something else, as opposed to instead something harder to recontain being breached alongside the other thing. Like, this is an extreme example, but TG alongside 8837 is going to be far more difficult, than 860 alongside TG.
- + Would potentially encourage more RP with 860 & RsD activity - ...Strange, right? Adding something to the pool of 'what can breach' would in turn encourage an RP interaction. My point here is generating interest in 860. We already made 912 able to speak via RP events; So why not do more? Have RP events that accompany 860's sudden ability to breach. Encourage use. This would additionally be fun for GOIs to be able to capture an SCP that they previously were unable to outside of events or very rare, special circumstances.
Possible Negatives of the suggestion:
- - Underutilisation - Imagine, you add breaching behaviour to 860 and as a result... People still just don't play 860 that much anyway. Even worse, it may take activity away from other underplayed SCPs. Or it just doesn't have the intended effect, which is also a possibility.
- - Dev time - Working out balance, etc. As I said above. But it'd be significantly less than implementing an entirely new breaching SCP, as this is existing server content.
- - Size/Space issues - Since 860-2 wasn't designed for breaching, it may have issues with collision size when it comes to moving around the map, which can cause issues for both its gameplay and being recontained, especially that its CC is awkward to navigate with a cuffed entity in tow (although this in particular can be avoided by making it terminable) and that one of the doors leading into the 860 dimension is unbreakable by SCPs(?).
- - Lore inaccuracy - As much as I think I've reasonably justified everything I've stated here, there is still the issue that this would be out of the bounds of what is largely seen as "canon" of 860; However, I believe this in particular is minor and falls within the bounds of creative freedom. Again, I believe that I've reasonably justified all of this. This is not too far-fetched, in my opinion.
Based on the Positives & Negatives, why should this suggestion be accepted:
When I suggested this before, it was just a trial idea to workshop a 914 breaching suggestion. After looking back, I recognise that this specific idea was well-received by the community enough, as well as numerous other considerations regarding the server and how it plays right now.One thing I have noticed is that players seem to really want a new SCP - Which I understand why that time, effort and resources can't really be spared for a new SCP for the time being; I think the next best thing would be to grant 860-2 breach behaviour. It's not really a "new SCP" per se, but it being seen around the site would be a new thing. And it could be captured by surface GOIs for their enjoyment. And it's already sampleable, with a useful chem (although the chem has combative applications)! ...I agree with the prospect of its novelty not lasting long and wearing off after a short while, then players will be back to wanting a new SCP - However I think it has enough other benefits (breach variety, giving more use to those specific map areas, especially given 860 takes up a significant amount of space, etc.) to be worth consideration in the meantime.
As for my gripe about the prior denial - While I've made it clear that the given reason of it not making sense when I specifically framed it and presented it in a way that either should make sense or be otherwise made to make sense at the discretion of whoever, I didn't contest it at the time because I also get the general hesitancy behind diving into the weeds with 860. Balance implications, bug implications, etc. How used it would be, considering that 860's CC is directly above lecture hall, meaning that it wouldn't be a viable hacking target given that you can hear things happening in that CC from PW. At the time last year, I was able to see and understand why it may not be reasonable to pursue this developmentally.
As things are now, aside from the drawbacks I've listed above, I don't really see a reason not to pursue this if at all possible. Unlike adding a completely new breaching SCP, this is an existing SCP - Meaning that this is virtually feature-complete and would for the most part, just need adjustments to account for it being able to breach, being balanced when breached and not being too disruptive to the server overall. There would not need to be any new assets or mechanics developed for this implementation. It would be an extremely efficient use of what we have as is.
860-2 being able to breach would give new life to a largely overshadowed and underused portion of server content and map space. I think it would be exciting for existing players seeing a fresh face in the breach rotation and also give newer players getting into the server learning how it works, a breaching SCP to play around with, rather than being underwhelmed with 860's current status as a purely roleplay and set piece and may encourage user retention, since they would have a larger variety of SCPs to breach as, that is unless its SCP level requirement is raised (Which I'd understand bringing it up a little in addition to making it able to breach).
This could also help discourage abuse of 860 itself - Even though it's already against the rules to use 860 to survive the nuke, the fact of the matter is, it's pretty difficult to enforce. I imagine there have been people that have done it as a way of abusing it to preserve say, 914 disguises and gains as a D-Class? But have simply not been caught, because who checks 860 after a nuke? If there's someone on 860 waiting for a breach, then that could discourage people from abusing it. Additionally, I am aware of a significant amount of weird mingery that happens with 860, too. As it is right now, it's a strange blind spot that's just... There. I recall a recent 008 breach where I got to be a -2, and I went into the CC exterior to find three Tech Experts sitting inside the CC, behind the unbreakable door, but not in the dimension. We kinda just screwed around until some spores started growing in the CC, at which point the techies went into 860 proper - I don't know what happened to them after that because I left the area, but I imagine they survived the ensuing nuke. There are also occasions where people will just randomly dip into 860 for whatever reason.
...Fuck, this is hard, how do I convince you that this is a good idea? Please do it
I'm tired. I'm trying, but I'm just really not seeing why it shouldn't be allowed to breach. The only other thing I can think of, is that the plans to remove 860 are still on the table, as @Auburn mentioned in the prior suggestion discussion. 
That idea makes sense given its current underutilisation and how much space it takes up in both map space and filesize. I would like to state that it is an SCP beloved by the community and what I'm suggesting here would provide justification to its presence on the server. 
Additionally, letting 860-2 breach would also guarantee the announcement of Half Life 3, fr fr.
