Step-by-step guide

Use the r2modman Config Editor without losing a working setup

Edit supported mod configuration one change at a time, document the baseline, and recover from invalid values.

GuideFor: New r2modman users and players who want repeatable, recoverable mod setups.Updated September 13, 2026
01

What the Config Editor does

The editor exposes supported configuration files through the profile interface so you do not need to hunt through folders. It does not explain every mod-specific option, validate every possible value, or repair a broken plugin. Keep the mod README open when an option’s units, range, or multiplayer effect is unclear.

02

Capture a baseline before editing

Record the profile name, package version, and original value. For important configs, copy the file before changing it. Modify one setting, save, and launch; several simultaneous edits make it impossible to tell which value caused the new behavior.

03

Prioritize high-impact settings

Server rules, world generation, network behavior, key bindings, and performance settings deserve explicit notes because they can affect other players or persist across sessions. When sharing a profile, document why a non-default value exists and whether every participant needs it.

04

Recognize files the editor may not expose

Some mods use JSON, YAML, databases, or custom files that do not appear in the editor. An empty editor does not prove the mod has no configuration. Use the profile’s data location and the package README to identify the real file before editing anything manually.

05

Recover from a bad configuration

Restore the copied file or disable the recently changed package. Reproduce in a cloned profile with default configuration, then reintroduce changes individually. Avoid deleting an entire profile before you know whether one value or one package is responsible.

Frequently asked questions

Clear answers before you change anything

Does Config Editor back up every change?

Do not rely on it as a backup system. Copy important files or preserve a profile export before significant configuration work.

Why is a mod missing from Config Editor?

It may not create a supported configuration file, may not have run yet, or may use another format. Check the mod documentation.

Are settings shared across profiles?

That depends on where the mod writes its configuration. Verify the active profile and actual file path before assuming isolation.

Research note: September 13, 2026 snapshot. Release assets and platform behavior can change; verify important details again before installation.

Recommended path: read this guide → download or create a minimal profile → record the result → expand to the full modpack.