Demo Language Change Fix

If the Emberville demo language change is not working, close the game and reset only options.eopt in AppData\LocalLow\CygnusCross\Emberville\Saves\. This is the documented workaround for language selection failing on some systems. Removing that file returns the game to its default configuration; it does not erase your character save when you delete only that file.

This remains a known issue in Demo Alpha 0.20.18.x, the latest verified public demo patch as of October 28, 2026. Earlier localization fixes do not mean every language-switching problem has been resolved. Start with the narrow options reset below rather than clearing the Saves folder or creating a new character.

Identify the language problem before changing files

A language selection that refuses to change is different from text displaying incorrectly after a language has already been selected. The first symptom is the one covered by the options-file workaround. The second may involve a particular line of dialogue, font rendering, text size, or an untranslated interface label. Both can be frustrating, but they need different descriptions when you check whether the reset helped.

Before closing the demo, note the language that currently appears in the interface and the language you are trying to select. Check a stable label such as a menu heading rather than a single character name. Proper names may remain the same across languages, so they are poor indicators of whether the entire interface switched.

If only one dialogue line is wrong while menus show the chosen language, record that line separately. Resetting your options may change the global language setting, but it cannot be assumed to correct every individual translation. Likewise, selecting another text language does not establish that the game provides another spoken voice track.

Reset only options.eopt

The path below is the Windows location given for this workaround. It identifies the game's local configuration area. It is not an instruction to delete the folder that contains it, and it is not a complete manual save-transfer procedure.

1. Close Emberville completely before editing its local files. Do not leave the demo running behind File Explorer while you remove the configuration file.
2. Open your Windows user profile's AppData folder, then follow LocalLow, CygnusCross, Emberville, and Saves.
3. Locate the file named options.eopt. Read the complete filename before selecting it, especially if Windows hides familiar filename extensions.
4. If you want an extra recovery copy, copy that one file somewhere outside the game's folder before removing the original. This is a precaution, not a required part of the documented workaround.
5. Delete only options.eopt. Leave all other files and subfolders untouched.
6. Start the demo again. Expect default configuration settings, then try selecting your intended language.
7. Check the interface labels again and confirm that your existing character remains available.

The important boundary is the filename. A folder called Saves can contain more than one kind of data. The workaround targets the options file inside it; the folder's name does not make its entire contents expendable. Do not use a broad cleanup command, select every file, or remove the parent Emberville directory.

If you cannot confidently identify options.eopt, stop before deleting anything. A spelling mismatch, a different user profile, or an unfamiliar directory is a reason to verify the location. Do not substitute an unrelated options file from another game merely because its name looks similar.

Expect other settings to return to defaults

The workaround restores default configuration, so treat it as an options reset rather than a language-only toggle. After the demo starts again, review the settings that affect how you play. For example, check your current input assignments before using a remembered shortcut. Do not assume that every customized preference survives a reset whose purpose is to rebuild configuration.

This does not mean you need to change every setting immediately. First verify the specific result you wanted: the language selection can change, the interface displays the selected language, and the game can continue. Once those checks pass, restore personal preferences gradually. If you change everything at once, it becomes harder to tell which setting was involved if the problem returns.

Keep the backed-up options file separate while you check the result. Restoring it immediately could also restore the configuration state you were trying to replace. Only use that copy deliberately if you need to recover the earlier setup and understand that tradeoff.

For a shared computer, confirm that you are checking the same Windows profile used to play. The relative AppData location belongs to a user profile. Finding a similarly named folder elsewhere is not enough to establish that it is the active configuration used by your current session.

Compare menu text and dialogue separately; this preview image does not show a language-setting repair.

Separate language switching from localization fixes

The public demo has received several language-related updates, and they address different symptoms. Alpha Demo 0.20.17.x included fixes involving Simplified Chinese, Traditional Chinese, Japanese, Korean, cutscene language, fonts, and some text boxes. Demo Alpha 0.20.18.x added more localization and text fixes. Despite those changes, failure to change the language on some systems remained on the known-issues list.

That history explains why a player can be on a newer build and still need the options reset. A patch can fix a broken text box without fixing the configuration problem that prevents another player's language selection from applying. It is also possible to select a language successfully and then encounter a remaining text issue elsewhere.

Use the symptom, not just the word language, when deciding whether a fix applies. If selecting the language now works but a particular subtitle is missing, the selection workaround has done its job. Record the subtitle problem separately instead of repeatedly deleting configuration in the hope that every translation issue shares one cause.

Check the result in a repeatable way

After relaunching, choose your intended language once and inspect more than one screen. A main-menu label and an in-game interface label provide a better check than a single translated word. If the change appears correct, return to your existing character and confirm that ordinary navigation still works.

Close and reopen the demo normally once more if you want to check whether the selection persists. This is a verification step, not a promise that restarting cures the bug. The useful observation is whether your selected language remains in place in the next session. Keep that result separate from whether a particular scene has correctly translated text.

Do not begin a long new play session simply to test language persistence. A short, controlled check is enough to determine whether the option was applied and retained. If the language immediately reverts, note exactly when it happens: after leaving the settings screen, after loading your character, or after reopening the application.

For a gamepad user, also distinguish a failed selection from failed menu navigation. Demo Alpha 0.20.18.x includes controller navigation changes. If the cursor or selection never reaches the language control, that is different from selecting a language and watching the text refuse to change. A temporary mouse comparison can help identify that difference without altering your save.

If the workaround does not resolve the problem

Stop repeating the same reset once you have confirmed that the correct file was removed and default configuration returned. Repeating an unchanged action does not add useful evidence. Preserve the character save and record what happened during the controlled check instead.

Include the demo version, Windows setup, current and desired languages, and the stage at which the choice fails when reporting the issue. State whether removing options.eopt reset other options and whether the language still refused to change. That lets a developer distinguish failure to locate the active file from a configuration reset that genuinely did not help.

A useful report can be short: the version you are running, the exact menu action, the expected language, and the visible result. If possible, add a screenshot of the relevant interface state. Avoid attaching unrelated personal files from the Windows profile or a complete save directory when a clear description is enough to start the report.

There is no verified universal second file to delete, registry edit to apply, or launch command that resolves every remaining language case. Do not escalate from a documented single-file reset to broad local-data removal. If the demo is otherwise playable, preserve that working state while waiting for a later patch or a response about the specific symptom.

Keep the demo and future release separate

These instructions apply to the public demo's known issue and its documented Windows workaround. As of October 28, 2026, Early Access has not launched; its planned date is January 7, 2027. The options reset does not establish how settings will migrate to that release, and it should not be treated as a save-conversion method.

When a new build becomes available, check its version and language behavior before carrying over old troubleshooting steps. A future release may change how configuration is handled. For the current demo, the practical goal is narrow and checkable: rebuild default options, select the intended text language, and keep the rest of the Saves folder intact.