Localization Guide: Language Files, Mods, Maps & Saves
Localization in Timberborn covers where the game stores user files that need localization attention (maps, saves, custom content) across platforms and legacy asset names that may appear in different language packs or older versions. Knowing these locations helps translators, modders, and support staff find the files they need to edit or verify.
File locations by platform
Windows
- User documents for Timberborn are stored under the current user's Documents folder. For example:
- C:\Users<User>\Documents\Timberborn\
- Subfolders commonly encountered:
- Saves
- Maps
- (other user-generated or config files)
- User documents for Timberborn are stored under the current user's Documents folder. For example:
Linux (Steam using Proton / Wine)
- When using Steam with Proton/Wine, Timberborn user files are located inside the Proton compatibility prefix for the game:
- /steamapps/compatdata/1062090/pfx/drive_c/users/steamuser/My Documents/Timberborn/Maps/
- Adjust the path for your Steam library location; the numeric app ID (1062090) is used by Proton to isolate game files.
- When using Steam with Proton/Wine, Timberborn user files are located inside the Proton compatibility prefix for the game:
Notes on macOS
- The provided sources do not include an explicit macOS path. Use the standard Documents folder for the current user if needed (~/Documents/Timberborn/) or consult platform-specific Steam/Proton documentation.
What to localize / common items found in these folders
Maps
- Custom maps created or downloaded by players are stored in the Maps folder inside the Timberborn user directory shown above. Localizers may need to inspect map metadata or filenames when translating map names or descriptions.
Saves
- Player save files are stored in the Saves folder under the Timberborn user directory on Windows. Translators and QA may need to load saves to verify localized text within saved games.
Mod and custom content
- Third-party or user-generated content (maps, translated assets) will often be placed in these folders. Ensure file encoding and naming conventions remain compatible with the game.
Legacy / obsolete asset names
- The game and older versions or DLCs may include legacy asset names and image files that appear in different language contexts:
Iron Teeth).png — appears as an obsolete or replaced Bakery asset.- Bakery (Iron Teeth).png — the active or alternate Bakery asset filename.
- These legacy filenames can appear in localization resources or asset lists. When updating translations or replacing assets, preserve original filenames where the game expects them or update any references in localization tables/scripts accordingly.
Practical advice for localizers
- Back up the entire Timberborn user folder before making changes to maps, saves, or asset files.
- Work on copies of map or image files; do not overwrite original filenames unless you also update any references the game uses.
- Verify encodings: use UTF-8 without BOM for text files to avoid parsing issues.
- Test changes on the target platform. Paths differ between Windows and Proton/Wine on Linux; ensure your changes are placed in the correct user folder.
- When dealing with obsolete assets, check whether the filename is still referenced by the game or mods; remove or replace only after confirming it will not break content.
Summary
Localization work for Timberborn frequently requires accessing user files under the Documents/Timberborn directory (Windows) or the Proton/Wine prefix on Linux. Custom maps and saves live in Maps/ and Saves/ respectively. Be aware of legacy asset filenames (e.g., obsolete Bakery and Farmhouse images) when updating translations or replacing assets, and always test changes on the platform you target.