- Heroes Vow Three Kingdoms XUnity translation requires a Windows-focused setup and a correctly selected game executable.
- Patch the game files first, then configure the translator before launching the game.
- Online translation services need internet access unless the required text has already been translated manually.
- Windows regional settings can affect auto-translation, especially when text appears but no translation is generated.
- Steam Deck support is uncertain, because the referenced tools were developed and tested for Windows.
Heroes Vow Three Kingdoms XUnity translation setup
Heroes Vow Three Kingdoms XUnity translation is a community-supported way to read more of the game through machine-assisted and manually prepared translations. The setup involves two related parts: a replacer utility for inserting translated JSON files and a BepInEx-based translation layer for additional files.
The safest approach is to treat the process as a game-file modification. Keep the original installation intact, verify the files before patching, and avoid mixing files from unrelated translator releases.
ReplacerUI
- Selects the game executable
- Inserts replacement JSON files
- Requires repatching after updates
BepInEx Layer
- Handles additional translation files
- May cover files outside the main replacement folder
- Uses a separate translation directory
Online Translation
- Generates text through an online service
- Requires internet access
- Can be affected by service limits or bans
| Component | Main role | Important note |
|---|---|---|
| ReplacerUI.exe | Applies replacement files | Select the actual game executable |
| Translations folder | Stores inserted JSON replacements | The utility may process only this folder |
| Translation folder | Stores BepInEx translation files | These files may be loaded separately |
| Online provider | Generates machine translations | Internet access may be required |
Use a clean, verified installation before applying any translator files. This makes it easier to identify whether a problem comes from the game update, the patch, or the translator configuration.
Step-by-step XUnity Translator installation
Follow this sequence when setting up the translator on a Windows installation. The exact archive structure can vary between releases, so always read the included instructions and avoid renaming files unless the release specifically requires it.
Verify the game installation
Open your Steam Library, access the game properties, and run the file-integrity check from the Installed Files area. Wait until the process finishes before extracting or applying the translator.
Extract the translator package
Extract the ZIP, RAR, or folder package to a temporary location. Keep the extracted folders together so ReplacerUI.exe can find its supporting files.
Launch ReplacerUI
Open the extracted folder and run ReplacerUI.exe. If Windows displays a security warning, confirm that the file came from the intended translator package before continuing.
Select the game executable
Choose Select game path, browse to the local game files, and select ThreeKingdom.exe. Selecting a parent folder or an unrelated executable can prevent the Start patching button from becoming available.
Apply and test the patch
Start the patch and wait for the completion message. Launch the game afterward. The first launch may take longer while files are initialized, so allow the process time to finish.
| Setup stage | Expected result | If it fails |
|---|---|---|
| File verification | Steam reports the installation is ready | Repeat the check before patching |
| Archive extraction | ReplacerUI.exe and support files are visible | Extract again to a simple folder |
| Path selection | Start patching becomes available | Select ThreeKingdom.exe directly |
| First launch | The game opens with the patch applied | Check file placement and logs |
| Game update | Translator files may need reapplication | Repeat path selection and patching |
The patch may need to be applied again after a game update. Keep the translator archive available rather than deleting it after the first successful installation.
A game update can replace or invalidate modified files. If the translator stops working after an update, verify the installation again and repeat the patching process instead of stacking another patch over the old one.
Troubleshooting missing or incomplete translations
A successful patch does not guarantee that every line will be translated automatically. The community troubleshooting pattern points to several separate causes: blocked network access, translation-service limits, Windows regional settings, incomplete folder handling, and unsupported environments.
First, check whether the translator interface opens correctly. If the hotkey works but no text changes, the problem may be with the online provider, system locale, or the selected translation mode rather than the patch itself.
| Symptom | Likely cause | Recommended check |
|---|---|---|
| Translator opens but text stays unchanged | Online service unavailable or blocked | Confirm internet access and provider settings |
| Only previously translated text appears | Online translation is disabled | Check firewall and network permissions |
| Translation starts after changing Windows format | Regional or system-language mismatch | Test a US-format Windows region |
| Some files are translated and others are not | Two translation systems are being used | Check both Translations and Translation folders |
| Patch works on Windows but not Steam Deck | Compatibility may vary on Steam Deck | Test on a supported Windows setup |
One reported solution for inactive auto-translation was changing the Windows region and system format to a US configuration. This should be treated as a troubleshooting test, not a universal requirement. Record your original settings before making changes so you can restore them later.
The translator may also rely on more than one file location. A common arrangement uses replacement JSON files in a Translations folder and additional BepInEx files in a separate Translation folder. If only the first folder is processed, some text may remain untranslated even though the main patch appears successful.
Test in this order: confirm the executable path, check both translation folders, confirm network access, test the Windows regional format, and then review compatibility with your platform.
Files, privacy, and platform compatibility
Translator tools can interact with local game files and online translation services. Before using one, decide whether you are comfortable with the tool modifying the installation and sending text to a third-party provider. A virus warning or browser flag does not by itself prove malicious behavior, but it should not be ignored.
Use the Heroes' Vow: Three Kingdoms Steam discussion as a reference for the community installation conversation. The discussion also identifies Windows as the environment targeted by the referenced DLL and EXE tools, while Steam Deck and Linux compatibility was not tested by the developer mentioned there.
| Environment | Compatibility guidance | Practical recommendation |
|---|---|---|
| Windows PC | Primary environment discussed for the tools | Use this for the initial setup |
| Steam Deck | Not tested for the referenced EXE and DLL | Expect additional troubleshooting |
| Linux desktop | May require Windows compatibility layers | Do not assume the patch will work |
| Offline play | Possible for already available translations | Online auto-translation will not function |
| Online play | Not automatically required to launch the game | Network access may be needed for machine translation |
A blocked connection can leave only manually prepared translations available. Conversely, a translation provider may restrict requests if it detects excessive usage. If one provider stops responding, review the translator’s supported alternatives rather than repeatedly sending failed requests.
Before applying files, make a backup of the game’s configuration and any existing translation folders. Do not overwrite unrelated mod files without checking whether they belong to the same framework.
Before Launching the Patched Game:
- Verify the game installation before applying files
- Keep a backup of existing configuration and translation folders
- Confirm that ThreeKingdom.exe is the selected executable
- Review network permissions for online translation
- Test the setup on Windows before troubleshooting Steam Deck or Linux
Online translation can send game text to a third-party service. Review the provider settings, use trusted files, and stop if the package source or requested permissions cannot be verified.
Recommended workflow and FAQ
The most reliable workflow is incremental. Patch a verified installation, launch the game, test a small amount of text, and only then adjust network, locale, or folder settings. This prevents several changes from hiding the original cause of a failure.
| Goal | Preferred action | Avoid |
|---|---|---|
| Restore a broken patch | Verify files, then repatch | Applying several archives together |
| Fix no auto-translation | Check internet and provider settings | Assuming offline mode generates new translations |
| Fix partial coverage | Inspect both translation folders | Removing files without checking their role |
| Prepare for updates | Keep the original package ready | Expecting the patch to survive every update |
| Test another platform | Start with Windows behavior | Treating Steam Deck results as identical |
Q: Does Heroes Vow Three Kingdoms XUnity translation require offline play?
No. The game does not have to be played offline simply because the translator is installed. Online access may be required for machine translation, while manually prepared translations can remain available without that service.
Q: Why does the translator open but translate nothing?
Check whether internet access is blocked, whether the selected provider is responding, and whether Windows regional settings are compatible with the translator. A working hotkey only confirms that the interface opened.
Q: Why are some files translated while others remain unchanged?
The setup may use both a Translations folder for replacement JSON files and a separate Translation folder for BepInEx files. Confirm that both parts of the package were placed correctly.
Q: Will the translator work on Steam Deck?
Compatibility is uncertain for the referenced tools because their EXE and DLL components were developed for Windows and were not tested on Steam Deck. Windows should be treated as the baseline environment.
The key principle is to separate installation problems from translation-service problems. If ReplacerUI cannot patch the game, focus on file verification and the executable path. If the game launches but generated translations are missing, focus on network access, provider limits, regional settings, and the correct translation folders.
Make one change at a time and test after each change. This produces clearer results than replacing every file or changing platform, locale, and network settings simultaneously.