Troubleshooting

"No EVE installs detected"

The app looks in the standard locations for your platform and did not find a settings directory in any of them.

Open Settings and set the path by hand. You are looking for the folder that contains files named core_char_<id>.dat and core_user_<id>.dat, or a folder containing the settings_* directories.

It refuses a folder with no core_*.dat files in it, with selected folder doesn't look like an EVE settings folder. That error means the path is wrong, not that the app is broken. Go one level deeper, or one level up.

If you run EVE through something unusual, like a non-Steam Proton prefix, a Lutris install or a second drive, the manual override is the supported answer.

The app says EVE is running

A running client was detected, so copies, template applies, snapshots and restores are all refused.

This is deliberate. EVE writes its settings files out when it exits, so anything written while the client is live gets overwritten the moment you log out.

Close every EVE client and the launcher. The app re-checks every few seconds and the warning clears on its own. It matches processes named exefile.exe, evelauncher* and eve-online*, so a launcher you forgot about in the tray will keep the lock on.

Characters show as numbers instead of names

Name resolution goes through the public ESI API. Numeric ids mean that call did not come back. You are offline, ESI is down, or something on the network blocked it.

Nothing is broken. Ids are how the files are keyed on disk, so copying, grouping and templates all work exactly the same. Hit Refresh once connectivity is back.

A copy skipped a character

Skips are reported with a reason and are usually correct. The usual causes:

  • The character is the source of the copy.
  • No file for that character exists in any detected settings directory, which is common for a character that has never logged in on this machine.
  • The source account's core_user_*.dat does not exist, so only the character file was copied.

Account settings did not come across

The character-to-account mapping is read from the EVE launcher's logs, which only record it at login. If the source character has not logged in since the launcher started keeping those logs, the app cannot tell which account it belongs to and copies only the character file.

Log in on the source character once, quit, hit Refresh, and copy again.

Push to the remote fails

Check, in order:

  1. A personal access token is set, and it has write scope on the repository.
  2. The token has not expired. Most hosts expire them by default.
  3. The remote URL is right, and the repository exists.
  4. The remote is HTTPS. Token auth does not apply to SSH remotes.

Snapshots and restores are entirely local, so a broken remote never stops you from versioning your settings, only from syncing them.

Something else

Open an issue on Github or ask in the Discord. Include your OS, and whether the install was detected automatically or set by hand.