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

Hardsuits Fire Protection #1445

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

VMSolidus
Copy link
Member

Description

I have incredibly vivid memories from SS13 over a decade ago. In particular, every time the Supermatter delaminated, one of the Engineers would inevitably end up heroically sacrificing themself by walking directly into the supermatter core in order to drag the crystal to space. This was made only possible because the engineering suits made you immune to fire damage. It's currently not possible for engineers to do this, since fire damage is ABSURD, and having an 80% reduction to 400 damage per second is still death in less than 3 seconds.

So this PR corrects the injustice. Now the chief engineer gets to heroically sacrifice himself by dragging the supermatter crystal out to space.

Changelog

🆑

  • add: Engineering Hardsuits, Maxim Hardsuit, and Cybersun's Elite Tacsuit now all make the wearer immune to atmos fires. Have fun walking directly into the supermatter engine. Play our your heroic engineer fantasy by dragging the supermatter crystal to space in order to save the station.

@github-actions github-actions bot added the Changes: YML Changes any yml files label Jan 6, 2025
@BlueHNT
Copy link
Contributor

BlueHNT commented Jan 6, 2025

Uhhhhh... Let me just make this lil part clear.

It is atmos suits which are supposed to be completely fireproof, not normal engineering ones, those are equipped with radiation proofing.

Also from the Syndicate, only the elite suit had full fire proofing. The rest had only partial.

Edit:

So it wouldn't be injustice, but complete unfairness towards atmosia and elite hardsuit, rather than the rest of em.

@github-actions github-actions bot added Changes: C# Changes any cs files Changes: Localization Changes any ftl files Changes: Sprite Changes any png or json in an RSI labels Jan 7, 2025
Copy link
Contributor

github-actions bot commented Jan 7, 2025

RSI Diff Bot; head commit 4d6081d merging into 975c905
This PR makes changes to 1 or more RSIs. Here is a summary of all changes:

Resources/Textures/Interface/Actions/psionics.rsi

State Old New Status
assay Added

Copy link
Contributor

github-actions bot commented Jan 7, 2025

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@github-actions github-actions bot added the Status: Merge Conflict FIX YOUR PR AAAGH label Jan 7, 2025
@Remuchi Remuchi added the Status: Do Not Merge Do not merge label Jan 7, 2025
@Remuchi
Copy link
Contributor

Remuchi commented Jan 7, 2025

I'll add Do Not Merge until you unfuck your pr

@Remuchi Remuchi added Size: 3-Medium For medium issues/PRs Priority: 3-Medium Needs to be resolved at some point labels Jan 7, 2025
@github-actions github-actions bot removed the Status: Merge Conflict FIX YOUR PR AAAGH label Jan 11, 2025
@VMSolidus VMSolidus removed the Status: Do Not Merge Do not merge label Jan 12, 2025
@VMSolidus
Copy link
Member Author

I'll add Do Not Merge until you unfuck your pr

PR is unfucked

@sleepyyapril sleepyyapril requested a review from Remuchi as a code owner January 23, 2025 01:32
@github-actions github-actions bot added the Status: Needs Review Someone please review this label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changes: C# Changes any cs files Changes: Localization Changes any ftl files Changes: Sprite Changes any png or json in an RSI Changes: YML Changes any yml files Priority: 3-Medium Needs to be resolved at some point Size: 3-Medium For medium issues/PRs Status: Needs Review Someone please review this
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants