Skip to main content
Timberborn Wiki

Mods Guide: Find, Install & Create Mods (Install Steps)

Mods expand Timberborn with new buildings, UI changes, maps, and gameplay mechanics; they are essential for players who want QoL improvements, community content, or entirely new systems. This page explains how mods are distributed, installed, created, and troubleshot, plus recommended types and safe practices.

What mods can do

  • Add new buildings, resources, and biomes using the official Mod API.
  • Provide QoL and UI improvements (Beaver management overlays, water overlays, intro skip, automation helpers).
  • Supply new maps and map-editor assets (custom starting positions, rivers, terrain, resource placement).
  • Introduce gameplay systems (trains, expanded terrain tools, creative mode).
  • Expose advanced integration points (HTTP Lever / HTTP Adapter for external automation and monitoring).

Timberborn’s mod ecosystem ranges from small cosmetic tweaks and overlays to large content packs that alter late-game progression.

Where to find mods

  • Steam Workshop — one-click subscription for Steam players; the most popular source for maps, tails, and many mods.
  • mod.io — the official cross-platform hub integrated into the game client.
  • Thunderstore — common for BepInEx/BepInExPack users and some legacy content.
  • Nexus Mods and community Discord channels — additional uploads, graphics, templates, and help.

Community resources also collect popular or recommended lists (e.g., BeaverBuddy, Water Overlay Enhanced, TimberbornTerrainTools, ChooChoo train mod).

How to install mods

  • Steam Workshop: Subscribe to items; they download automatically. Launch Timberborn, open the Mods menu, and enable the subscribed mods.
  • mod.io: Browse within the game or on mod.io, follow the platform instructions, then enable mods in the game’s Mods menu.

Manual install

  • Download the mod archive or files.
  • Extract into your Timberborn Mods folder:
    • Windows: %USERPROFILE%\Documents\Timberborn\Mods
    • macOS: ~/Library/Application Support/Timberborn/Mods
    • Linux: ~/.local/share/Timberborn/Mods
  • Launch the game and enable the mod in the Mods menu if required.

BepInEx / BepInExPack requirement

  • Many mods (especially code mods) require BepInEx or the community BepInExPack for Timberborn. Install BepInExPack by extracting its contents into the Timberborn game folder and running the game once to complete setup. Follow BepInEx documentation for plugin development and advanced usage.

Creating mods

  • Code mods are written in C# for Unity using the Timberborn modding SDK and BepInEx. An elementary understanding of C# and familiarity with BepInEx plugin tutorials are expected.
  • The modding SDK provides templates, examples, and API documentation; the official Discord has modding channels for support.
  • For graphics (banners, tail decals, custom images), use square PNGs (transparent 1024×1024 preferred) and community templates.
  • To share maps, use the built-in Map Editor then upload to Steam Workshop or mod.io; map files (.timber) live in the player Maps folder.

Enabling mods and save compatibility

  • Enable mods from the main menu’s Mods section after installation/subscription.
  • Mods that add new buildings, resources, or mechanics are safest when enabled at the start of a new save. Adding such mods mid-play may cause incompatibilities.
  • UI/QoL mods (overlays, displays) are generally safe to add to existing saves, but check each mod’s description.

Troubleshooting and common issues

  • Crashes on startup: disable mods one at a time to isolate the problematic mod. Version mismatches are the most common cause.
  • Conflicts: two mods altering the same system can conflict—check mod descriptions and author notes.
  • Save files: saves using mods may not load on a machine that lacks the same mods. Back up saves before enabling or disabling mods.
  • If a mod breaks after a game update, check the mod page for an updated version or revert to an earlier mod-compatible game version.
  • Game log files (Timberborn logs directory) contain error messages that point to problematic mods.

Best practices and safety

  • Back up your Saves folder before installing many or large content mods.
  • Prefer subscribing through Steam Workshop or mod.io for automatic updates.
  • Check mod compatibility notes and required dependencies (e.g., BepInExPack).
  • For your first time with mods, install light QoL mods (BeaverBuddy, Water Overlay enhancements) before large content mods to learn the flow.
  • Avoid enabling multiple mods that change core balance unless you accept altered achievements or gameplay.

Mod types and community staples

  • QoL/UI mods: improved overlays, beaver management UIs, intro skip.
  • Automation and integration: SmartPower-style tools and HTTP Lever/HTTP Adapter for external control/monitoring.
  • Content packs: new crops, buildings, biomes, and tech trees.
  • Creative and sandbox tools: Creative Mode, expanded terrain tools, map packs.
  • Cosmetic: tail decals, banners, custom images.

Sharing and publishing

  • Steam Workshop: use the in-game upload tools for maps and Workshop items; choose visibility, add descriptions and changelogs.
  • mod.io: follow mod.io’s upload guide for maps and mods; provide required metadata and assets.
  • When publishing, include clear compatibility (game version, required dependencies), changelogs, and installation instructions.

File locations and sharing

  • Mods folder (manual installs): Documents/Timberborn/Mods (platform-dependent paths above).
  • Steam Workshop content is stored in your Steam workshop content folder (Steam/steamapps/workshop/content/1062090).
  • Custom maps go into the local Maps folder; share .timber files or upload through the editor.

Use this guide to choose, install, and manage mods safely so you can expand Timberborn with confidence—from simple QoL tweaks to complex new gameplay systems.

Pages featured in this guide