Use the publisher’s edition instructions

Open the Saikey Studios product page from Sources and identify the package for the edition and language you own. The publisher gives a short instruction: select the matching package and copy its files into the game installation folder. Follow the live instructions and any package-specific notes rather than a third-party mirror.

The product page explicitly says that its own store download does not require this optional package. That instruction does not prove that the full-game package works with the demo. For that separate question, see Demo Patch Status.

Sponsored banner

Check the destination and protect your save

The instruction names the game installation folder as the destination. It does not name the save folder as a destination or provide a verified list of replacement files. As a general file-management precaution, close the game and make a separate copy of existing saves before changing installation files; see Save-file location.

The current product capture leaves its version fields blank and does not expose a complete success test or troubleshooting procedure. Do not infer compatible versions from the package name alone. For the distinction between native text support and an external translation, see English Support.

Keep Steam updates separate

The October 3 SteamDB snapshot lists public build 25550308 with September 26 build and branch-update timestamps. This is a third-party branch record, not a complete change list. The patch-history body ends in a load error and the Steam News capture does not expose announcement text, so neither establishes a later gameplay fix.

A publisher package, a Steam update and a separate product are different things. See DLC and related products before treating an associated listing as a gameplay expansion. Check Cheat table status separately before treating a memory-editing tutorial as a downloadable game resource.