Sulaco Crash Breach (Atmos discussion) (Poll Added)

[KingKire]

nope, if you have an exposed space tile and the rasp has any open area next to that tile, it will empty all the air of the exposed sulaco.


Now, my opinion for breaching is that, yes it should breach to space. BUT after a minute or so, it should automatically lock itself down. I say this because, its nice to see a lack of atmos in one room of the ship. it is not cool to see the whole ship be vented out through that single exposed tile due to SS13 quirks. Unfortunately, CM does not have an ability for the engineering staff to quickly repump a room full of oxygen like what you would expect from a future-based WARspaceship. (Dragging an oxy canister and opening it is not a good solution to hullbreaches). until we do have that pumping ability, i say lock down the hull after 1-2 minutes of breach. call it an "automatic hullsealer"

[TastyCrabLegs]

I don't know if this is still a subject, but here's my Two Cents: Crashing is fine. However, RANDOM crashing isn't.

In practice, this is akin to not knowing which of the Sulaco will be randomly depressurized, gibbed, and xeno'd. How is that fun?

Remove the random crashing OR give an alert to what's going to be destroyed so you can plan for it. That way you can plan around the depressurization and destruction before it actually happens.

Also, I don't know if this changed, but if the Medbay shuttle crashing location still exists, remove it. That just sounds like a completely bad idea.

this is a well thought out solution

[Jroinc1]

nope, if you have an exposed space tile and the rasp has any open area next to that tile, it will empty all the air of the exposed sulaco.


Now, my opinion for breaching is that, yes it should breach to space. BUT after a minute or so, it should automatically lock itself down. I say this because, its nice to see a lack of atmos in one room of the ship. it is not cool to see the whole ship be vented out through that single exposed tile due to SS13 quirks. Unfortunately, CM does not have an ability for the engineering staff to quickly repump a room full of oxygen like what you would expect from a future-based WARspaceship. (Dragging an oxy canister and opening it is not a good solution to hullbreaches). until we do have that pumping ability, i say lock down the hull after 1-2 minutes of breach. call it an "automatic hullsealer"

We do have an ability to remotely re-pressurize rooms. It's called the vent system, but you have to hit 3 buttons in atmos to make it work, aand you can't weld vents that you want to have re-pressurize rooms...

[Epic_Charger]

Breach works, just should be more space suits and oxygen gear to deal with it when it happens.

[Karmac]

There are space suits, nobody uses them because there's no time for you to put the things on before you're swamped with ayys.

[Swagile]

And the space suits break from one claw hit, making you die from atmos anyway.

[RedsPro]

Breach makes it harder for the Muhreens. I kinda like it i wish the Ayys were slowed a lil or something with no Atmo just to even the odds a little

[Keban DaBrowne]

The breaching mechanic is definitely exciting and dramatic. On the fence about making dealing with atmos easier for marines somehow. However, after my second time being gibbed by a shuttle, I'd say that we need to know the room it's landing in, even if it's a four second warning. Just enough so that I can avoid being instantly killed by something I had zero opportunity to react against. There's really nothing like it elsewhere in the game.

[kroack]

The breaching mechanic is definitely exciting and dramatic. On the fence about making dealing with atmos easier for marines somehow. However, after my second time being gibbed by a shuttle, I'd say that we need to know the room it's landing in, even if it's a four second warning. Just enough so that I can avoid being instantly killed by something I had zero opportunity to react against. There's really nothing like it elsewhere in the game.

Getting sadared or mined as an ayyy is pretty close.

[Crab_Spider]

The crash breach no longer has the ability to cause atmos problems unless someone destroyed the front Rasputin window and it crashed into RnD/top deck medbay.

[MrJJJ]

The crash breach no longer has the ability to cause atmos problems unless someone destroyed the front Rasputin window and it crashed into RnD/top deck medbay.

Nope, it still causes them, esspecially since sometimes it crashes in places where a certain window might be open to space

[ExGame]

Well, from what I have seen some ERTs die immediately upon opening their shuttle window due to the fact that ERTs can only be called when the Rasputin crashed onto Sulaco aka. the Sulaco got depressurized, and since no ERT gets oxy tanks and only Mercenaries gain oxyless space suits it's kinda hard to deal with.

[Jroinc1]

Nope, it still causes them, esspecially since sometimes it crashes in places where a certain window might be open to space

Admins such as Feweh seal it off, and fix the atmos problems, so I'm pretty sure it's been quietly removed.

[MrJJJ]

Admins such as Feweh seal it off, and fix the atmos problems, so I'm pretty sure it's been quietly removed.

Last round nobody did it, despite admins on and mods, the staff can't always fix it neither can they always be there to do it, so no, its not removed.

[northcote4]

Admins such as Feweh seal it off, and fix the atmos problems, so I'm pretty sure it's been quietly removed.

As far as I'm aware, our current stance is to just left the Rasp crash wherever it wants. If it causes a breach into space, so be it.

The only exception is it if crashes into atmos, at which point we will try and stop atmosfuckery across the entire station.

[Feweh]

We stopped breaching, but it'll still sometimes pierce through the outer.

I'll seal it at times to promote a good fire-fight, or if the xeno's are really strong.

[Jroinc1]

We stopped breaching, but it'll still sometimes pierce through the outer.

I'll seal it at times to promote a good fire-fight, or if the xeno's are really strong.

Understood. I just wanted to confirm that it had been removed.