CustomCheckpoints

How does this mod work?

This mod uses a .json config file to add checkpoints to specific security doors. All players in your group need this mod installed, since it changes level data that must match between all clients. There is no User Interface for this mod, so you have to edit the file manually.

Where do I find the config file?

1. Run the game with the mod installed so a configuration file gets created.
2. Open the profile folder where you installed the mod.
3. Go to BepInEx/config.
4. There should be a file named CustomCheckpoints.doors.json.

How to configure checkpoints?

1. Open the config file using whatever text editor you're used to.
2. Search for the expedition where you want to add checkpoints to.
3. Change security doors into a checkpoint by setting the IsCheckpoint field to true.

Do I need to restart the game for changes to apply?

No, the mod reads the file right before you drop into an expedition, so you don't need to restart the game after making changes. You do need to fully leave and restart the expedition for changes to apply to a level you're already in.

How do I verify the mod works?

After having dropped into a level, open the log file at BepInEx/LogOutput.log in your profile folder and look for lines like this:

[Info   :CustomCheckpoints] Adding a checkpoint to Door to zone 50
[Info   :CustomCheckpoints] Adding a checkpoint to Door to zone 52
[Info   :CustomCheckpoints] Added 2 checkpoints.

This depends on what you changed of course.

Important notes

• The mod hasn't been widely tested, so it may not work with every modded rundown.
• If the file becomes invalid (e.g. broken JSON), the mod will reset it to defaults automatically, and you will lose all the changes you made.
• Do not change any other field, as that will reset the configuration.
• If you're a rundown developer, the separate CConsole mod may offer a more convenient way to set checkpoints.

Example