Why can a new build affect an older installation?
The Lichii README says the rebrand intentionally keeps existing Eden/Eglantine data directories and configuration keys. It does not move or delete saves, settings or shader caches as part of the rebrand.
That preserves continuity, but it also means you should not assume that two extracted program folders have isolated settings. The data-folder discussion #535 includes a report of conflicts with an existing Eden configuration. It is a specific user report, not proof that every installation is affected.
Make a backup before opening an experimental build
- Record the current build and any settings you need to reproduce. Keep the archive or program folder that previously worked.
- Locate the save for each game you care about. The repository’s inherited storage documentation describes a right-click Open save directory action. Use the path opened by your actual build rather than guessing a newly branded folder name.
- Note the surrounding emulator data location and any relevant configuration, input profiles or add-ons you want to preserve.
- Close the emulator fully before copying data. Store a dated backup outside the active data directory.
- Check that your backup contains files and that you know which game/profile it belongs to. A screenshot of the directory is not a backup.
The inherited log documentation uses Eden paths and also mentions a portable user folder. Those names reflect possible setups; your actual opened directory is the better starting point than a hard-coded assumption.
Install the new program files separately
Use official downloads and extract the complete package to a clearly named directory, for example one containing its build number. Read the release notes for changed requirements and known regressions.
Keep the previous program directory available while comparing. Do not describe this as perfect isolation: both applications may still open the same data. If you need isolated profiles or a portable configuration, follow the build’s documented method and verify where it actually writes before relying on it.
Compare one repeatable test
Use the same game version, save, hardware, driver and scene. Note whether the issue appears at startup, the intro, actual gameplay or save/load. If comparing PGO and standard, use the build comparison guide.
Do not overwrite your only backup with data from an unsuccessful experiment. Keep the original snapshot until you have checked the game and its save/load behavior in the new build.
Preserve logs before reopening
The inherited log guide describes accessing the log folder through the application. Some labels retain Eden wording. The active Ocarina crash tracker requests eden_log.txt and, when relevant, eden_log.txt.old.
Copy the affected session’s log before repeated launches replace useful context. Review it for personal paths or other private data before attaching it to an issue. Do not include game files, keys, firmware or private account information.
For the next step, use platform setup, compatibility reports or troubleshooting according to the actual result.