Introduction
Replicator Redux copies EVE Online UI settings from one character to another.
That is the whole pitch. EVE stores every window position, overview preset,
bracket setting, colour tag and shortcut in a per-character file on disk.
Getting a new alt to look like your main has historically meant either
copying .dat files by hand and hoping you picked the right ids, or
re-doing nine years of tuning from scratch.
This does it properly: it finds your installs, resolves the character ids to real names, copies the files, and keeps every change in a git repository so you can walk it back.
The four ideas
Characters. Every core_char_<id>.dat found across your EVE installs.
Pick one as the source, pick any number as targets, copy.
Groups. A named set of characters: your mining fleet, your incursion alts, the wormhole crew. Copy to the group and every member gets the profile in one action.
Templates. A snapshot of one character's settings, saved with a name and kept in the app's own database. Apply it months later to a character that did not exist when you saved it.
Snapshots. Every mutation is committed to a real git repository that mirrors your settings directory. Browse the log, restore any commit, and optionally push it to a private remote so the settings follow you between machines.
Where EVE keeps this
Settings live in a settings_* directory inside your EVE install, as two
kinds of file:
| File | Holds |
|---|---|
core_char_<characterId>.dat |
Per-character UI: windows, overview, tags, shortcuts |
core_user_<userId>.dat |
Per-account settings shared by that account's characters |
Replicator Redux discovers those directories for you:
- Windows:
%LOCALAPPDATA%\CCP\EVE\... - macOS:
~/Library/Application Support/EVE Online/p_drive/... - Linux (Steam Proton):
~/.steam/steam/steamapps/compatdata/8500/...and the Flatpak and Debian equivalents
If yours lives somewhere unusual, point at it by hand in Settings. See Installation.
Two rules it enforces
It will not touch anything while EVE is running. The client rewrites its settings files when it exits, so anything written underneath a live client gets clobbered. Replicator Redux polls for a running process and blocks every mutation until you are out.
Nothing leaves your machine. There is no account, no telemetry, and no server. The only network calls it makes are to the public ESI API, to turn character ids into names, and to your own git remote if you configure one.
Next: Installation.