Atmos - Remove Implementation?

From ChatGPT

Disabling the atmospherics code in SS13 depends on how integrated it is in your specific codebase. Atmospherics tends to be tightly woven into both the game logic and the map itself, so simply disabling it might lead to unintended consequences. Here’s a general guide on how you can disable or bypass atmospherics:

1. Comment Out/Remove Atmospherics System Initialization

Look for the atmospherics subsystems, which are typically located in files like code/modules/atmospherics/.
Find the initialization code that loads or updates the atmospherics system. This is usually in a file like ssatoms.dm or within SSinitialize/InitializeSubsystems.
You can comment out or remove any code related to initializing atmospherics subsystems.

2. Modify Map to Remove Atmospherics Components

Atmospherics interacts with pipes, vents, scrubbers, and air in almost every room on the map.
Remove these components from the map .dmm files to avoid any dependencies that could cause errors or crashes.
Be aware that this might break some systems reliant on air like life support, so testing is crucial.

3. Disable Atmospherics Processing

The atmospherics system uses a lot of processing for calculations. To disable it:
- Find any processes related to atmos in files like process_atmos.dm.
- Either comment out or significantly reduce the frequency of atmosphere updates by adjusting how often the atmospheric subsystems run.

4. Disable Atmosphere Code in Airlocks and Breathing Systems

Many parts of the game will still reference atmos, such as airlocks and breathing mechanics.
You may need to search for instances where atmos is being checked and bypass or comment out those checks. For example, airlocks will often check for pressure differences when opening.

5. Stub Out Atmospherics Procs

Another approach is to stub out functions related to atmospherics. Replace the function bodies with an empty block (return statements) so that the functions don't do anything, preventing crashes or errors.
This can be done in code/modules/atmospherics/air.dm, code/modules/atmospherics/gas_mixture.dm, etc.

6. Test Thoroughly

After making changes, thoroughly test the game to ensure that removing atmospherics doesn’t lead to runtime errors, crashes, or unintended side effects (like rooms not filling with air).
Pay special attention to areas of the game that expect atmos systems to work, such as space exposure, hull breaches, and life support systems.

Disabling a core system like atmos is tricky because it’s so deeply integrated into the game's core logic. You might also consider selectively disabling atmos in certain areas or creating a simplified system if fully removing it causes too many issues.

Let me know if you need more detailed instructions on a specific part of this process.

Offwrldr / Nekoma