Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Alternatively, and maybe simpler, you could provide your game "unpackaged" (as in, the game's files will technically be viewable and accessible to the player, rather than packaged into the .exe) and then just give people "chapter" folders that they would drag into the "data" folder of their game, which would add them to the base game. In this version, you really just need to have your "patch" match the base folders, e.g.:
Base
> data
- bgimage
- fgimage
- bgm
- sfx
- scenario
Patch 1
> data
- bgimage
- fgimage
- scenario
(The local patch choices does about this same thing, except that you can work with packaged contents if you don't want players to be able to access assets).
Let me know if that helps and you need me to clarify either process.
[apply_local_patch file="file.tpatch" reload=true]
And then have players drop the tpatch file you distribute (which you'll get if you follow my guide) into the main folder with the .exe.