Seraph keeps a single per-user data folder shared across every supported client (Lunar, Badlion, Forge). Switch clients and your settings come with you.
File location
| OS | Path |
|---|
| Windows | %AppData%\Seraph\ |
| macOS | ~/.Seraph/ |
| Linux | $XDG_DATA_HOME/Seraph/ (defaults to ~/.local/share/Seraph/) |
config.json, your settings.token.json, Seraph auth token. Don’t share this.nicknames.json, saved nick to real-name mappings (only entries you marked permanent).
Blacklist data isn’t stored locally, it lives on the Seraph backend and is fetched on demand.
Run /seraph config (or /sconfig). The menu has six tabs: API, Overlay, Anticheat, Misc, Tags, Experiments.
Search
The search bar at the top indexes every entry from every tab. Type a keyword (fkdr, cape, flag, auto gg) and it’ll find every matching setting.
Conditional entries
Some settings only show in their tab when a parent toggle is on (e.g. the alert sound only appears when alerts are enabled). Search ignores those gates and shows them anyway, with a note explaining what to enable first.
Manual edits
Don’t edit config.json while the game is running, Seraph rewrites the file when you change settings, so your edits will be lost.
config.json directly while the game is closed. Seraph picks up changes on the next launch.
If you imported an older config and Seraph complains it’s out of date:
Reset to defaults
Delete config.json while the game is closed. On next launch, Seraph rewrites it with defaults.
Sharing configs
Make sure to remove your API Keys saved in the configuration file.
config.json is portable. Copy it to a friend (or a different machine) and they get your exact setup.
Don’t include token.json: it’s bound to your account and only works for you. 