timberborn-modding

You patch Timberborn JSON by applying targeted JSON content mods that adjust existing Blueprint values. This process modifies game data directly without altering core files, ensuring changes remain coherent and easily manageable.

Route A and Route B are two distinct scaffolding paths for new Timberborn building assets. They differ in handling templates, materials, and localization, letting you choose the appropriate workflow for your specific asset requirements.

You need BepInEx or Harmony when creating C# DLL or UI mods for Timberborn. These frameworks are required for implementing in-game settings, generating dynamic JSON, or adding complex behaviors that JSON patches alone cannot achieve.

Yes, you can bundle multiple Timberborn JSON patches into a single JSON adjustment pack. This keeps modifications coherent and organized, ensuring related balance changes are applied together as a unified mod.

Yes, this Timberborn modding workflow requires local validation and docs build processes. It mandates valid SKILL.md frontmatter, a properly formatted agents/openai.yaml interface, and a repository structure with references and templates.

JSON content mods for Timberborn are limited to modifying existing Blueprint values and cannot introduce dynamic behavior. For in-game settings, generated JSON, or complex interactions, you must use C# DLL or UI mods with BepInEx.