8000 Fix chemfire survival on simulated turfs by Egregorious · Pull Request #23803 · goonstation/goonstation · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fix chemfire survival on simulated turfs #23803

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

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

Conversation

Egregorious
Copy link
Contributor
@Egregorious Egregorious commented Jun 11, 2025

About the PR

Chemfire hotspots don't check for toxins in the air on their tile when deciding if they should self destruct.

This change makes it so that chemfires on simulated turfs will correctly heat up and apply burning to mobs which remain inside them.

Why's this needed?

Chemfires seem to be supposed to last for 3 seconds. On simulated tiles however, they currently last for only 2 seconds and self destruct before they enter their first atmos process cycle proper because they expect to see combustable gas in the atmosphere. Whereas the implication of a chemfire is surely that the chemical is what's burning.

It also means that chemfires never burn anyone unless they are actively stepped inside, thus you can 'dodge' a flashfire by standing still, which is rather wonky.

In practice this does increase the duration of almost all on-station chemfires by 50%, so reducing the default to 2 seconds may also be appropriate in terms of balance.

Testing

Tested by standing inside fires made by fireball and the vega flamethrower, and noting that burn duration increased.

Changelog

(u)Egregorious
(+)Chemfires are more consistently harmful to stand in. 

@keywordlabeler keywordlabeler bot added A-Status-Effects Deals with status effects of any kind C-Bug A bug that impacts usage of a feature labels Jun 11, 2025
@github-actions github-actions bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 11, 2025
It made sense to package in a previous iteration, but it's just extra now. Try to remember to PR when freeze ends
@github-actions github-actions bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. S-Merge-Conflict Applied and removed when a PR has or no longer has a merge conflict and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jun 11, 2025
@github-actions github-actions bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. S-Merge-Conflict Applied and removed when a PR has or no longer has a merge conflict labels Jun 18, 2025
Copy link
Member
@frawhst frawhst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good fix.

In practice this does increase the duration of almost all on-station chemfires by 50%

badass

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Status-Effects Deals with status effects of any kind C-Bug A bug that impacts usage of a feature size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0