Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ripley still has no way of dealing with firelocks #34588

Open
Kadeo64 opened this issue Jan 22, 2025 · 7 comments
Open

Ripley still has no way of dealing with firelocks #34588

Kadeo64 opened this issue Jan 22, 2025 · 7 comments
Labels
A: General Interactions Area: General in-game interactions that don't relate to another area. D3: Low Difficulty: Some codebase knowledge required. Issue: Replicated This issue has been replicated by another user. P2: Raised Priority: Item has a raised priority, indicating it might get increased maintainer attention. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. T: New Feature Type: New feature or content, or extending existing content

Comments

@Kadeo64
Copy link
Contributor

Kadeo64 commented Jan 22, 2025

Description

If a firelock comes up near a Ripley, the Ripley is physically incapable of passing it without the pilot getting out and opening the firelock. This makes using the Ripley when atmos is poor complete suffering
Reproduction
step one: get in a ripley
step two: try and walk from point a to point b on a station with poor atmos quality
step three: get out every 10 seconds to open firelocks and then just drop the Ripley entirely because it's not worth it

Additional context
Ripley should probably be able to open non-emergency firelocks like crew can, and when the firelock lights are up the hydraulic clamp should probably be able to pry them open. I think the clamp can pry on /tg/station..?

@github-actions github-actions bot added the S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. label Jan 22, 2025
@ArtisticRoomba ArtisticRoomba added P2: Raised Priority: Item has a raised priority, indicating it might get increased maintainer attention. T: New Feature Type: New feature or content, or extending existing content D3: Low Difficulty: Some codebase knowledge required. Issue: Replicated This issue has been replicated by another user. A: General Interactions Area: General in-game interactions that don't relate to another area. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. and removed S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. labels Jan 22, 2025
@ps3moira
Copy link
Contributor

Ripley's should just be able to pry open doors, maybe even powered doors?

@Kadeo64
Copy link
Contributor Author

Kadeo64 commented Jan 23, 2025

Ripley's should just be able to pry open doors, maybe even powered doors?

At first I thought this might be a bit powercreep; but science is capable of getting Jaws of Life at tier 2 industrial, so I think that this would be alright. maybe.

@deltanedas
Copy link
Contributor

if it can fight xeno queens why cant it pry open doors

@K-Dynamic
Copy link
Contributor

I wanted to add a pryable component to the ripley clamp but that would've let the clamp itself be used as a crowbar rather than the ripley action

@Kadeo64
Copy link
Contributor Author

Kadeo64 commented Jan 23, 2025

I wanted to add a pryable component to the ripley clamp but that would've let the clamp itself be used as a crowbar rather than the ripley action

it probably needs some new C# code which sucks

@ArtisticRoomba
Copy link
Contributor

type: tool qualities: prying not enough?

@deltanedas
Copy link
Contributor

mechs should have whitelisted interaction relay for doors imo, they can bump open doors anyway so it makes sense that you can open firelocks without getting out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: General Interactions Area: General in-game interactions that don't relate to another area. D3: Low Difficulty: Some codebase knowledge required. Issue: Replicated This issue has been replicated by another user. P2: Raised Priority: Item has a raised priority, indicating it might get increased maintainer attention. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. T: New Feature Type: New feature or content, or extending existing content
Projects
None yet
Development

No branches or pull requests

5 participants