Added debugger guide.

Author: datvm

ModdingGuide/ModdablePrefab.MD

@@ -0,0 +1,8 @@
+---
+title: "Make a code-less mod (using JSON) with Moddable prefab"
+description: A comprehensive guide to making mods for Timberborn
+date: 2025-03-13
+tags: mods timberborn guide modding
+---
+
+Placeholder content

ModdingGuide/attach-debugger.MD

@@ -0,0 +1,72 @@
+---
+title: "Attach a Debugger to Timberborn"
+description: A comprehensive guide to making mods for Timberborn
+date: 2025-03-13
+tags: mods timberborn guide modding debugging
+---
+
+[Home](../) / [Modding Guide](./) / Attach a Debugger to Timberborn
+
+**This guide can be done totally thanks to `normanr`. All credits go to him. I just made a few changes to make it easier to follow. Parts of this guide is from [dnSpy's guide](https://github.com/dnSpy/dnSpy/wiki/Debugging-Unity-Games#turning-a-release-build-into-a-debug-build) and [Let's Play with Fire Wiki](https://wiki.fireundubh.com/unity/turning-a-release-build-into-a-debug-build).**
+
+This short guide will show you how to attach a debugger to Timberborn and debug the game code or your mods using DnSpy and Visual Studio.
+
+- With dnSpy, you can debug the game code using the game's assemblies (DLLs) or ripped assemblies from AssetRipper.
+- With Visual Studio, you can debug your mod code.
+
+# Installation guide
+
+1. Determine and install the Unity version the game is using:
+    - Right click on the Timberborn executable and select `Properties`. Go to the `Details` tab and look for `Product version`. For example at the time of writing, the version is `6000.0.36f1`.
+![Timberborn executable properties](./img/unity-version.jpg)
+    - Go to [Unity Download Archive]( https://unity.com/releases/editor/archive) and download the corresponding version (you don't actually need to run it, just need some files from it).
+
+> **Tip:** while waiting for the download and installation, you should make a backup of your game's folder.  
+I myself even create  Git repository for the game folder, then create a branch called `dev-build` so I can easily switch between the dev build and the normal game because the Dev build does have a lot of dev UI that are not useful when you are not debugging the game.
+
+2. Go to this folder you just installed, `Unity 6000.0.36f1\Editor\Data\PlaybackEngines\windowsstandalonesupport\Variations\win64_player_development_mono`:
+    - Copy the content of the `Data` folder over to your game's `Timberborn_Data` folder, overwriting everything.
+    - Copy `WindowsPlayer.exe` + `UnityPlayer.dll` to your game's folder (where `Timberborn.exe` is). Rename or delete the original `Timberborn.exe` then rename `WindowsPlayer.exe` to `Timberborn.exe`.
+
+3. Edit `Timberborn_Data\boot.config` and add these two lines:
+
+```ini
+wait-for-managed-debugger=1
+player-connection-debug=1
+```
+
+4. (Optional) If you want to use Visual Studio, make sure you have "Game development with Unity" installed. You can check this in Visual Studio Installer.
+
+![Visual Studio Installer](./img/vs-unity-tools.jpg)
+
+That's it. If you use my tip above, now you can make a commit into the new branch `dev-build` and you can switch between the dev build and the normal game easily.
+
+# Debugging with DnSpy
+
+You can either use `Start` command or `Attach to Unity` command in DnSpy. Then you simply load the game's DLLs (either directly from the game folder or from AssetRipper) and you can put breakpoints and debug the game code.
+
+![DnSpy Start](./img/dnspy-start.jpg)
+
+For example, I put a breakpoint at `Timberborn.BlockSystem.BlockObjectFactory.CreateUnfinished` for when I want to know what happens when I build a building:
+
+![DnSpy Breakpoint](./img/dnspy-debug.jpg)
+
+# Debugging with Visual Studio
+
+> **Note:** in order to debug your mod's code, make sure you built your mod with embedded Debug symbols. You need this in your `csproj` file:
+
+```xml
+<PropertyGroup>
+    <!-- Others code -->
+    <DebugSymbols>true</DebugSymbols>
+    <DebugType>embedded</DebugType>
+</PropertyGroup>
+```
+
+Then when the game run, you can click `Debug > Attach Unity Debugger` in Visual Studio and select the `Timberborn.exe` process. You can put breakpoints in your mod's code and debug it like a normal C# project.
+
+![Visual Studio Attach Debugger](./img/vs-debugging.jpg)
+
+---
+
+[Back to Modding Guide](./)

ModdingGuide/img/dnspy-debug.jpg

@@ -30,8 +30,13 @@ Useful external links:
 4. _(Optional)_ [Useful knowledge of Timberborn architecture](./timberborn-architecture): My experience and knowledge about Timberborn's codebase that may come in handy when making mods.
 5. _(Optional)_ [Advanced Modding Techniques](./advanced-modding): Some techniques I use in my mods to make modding easier and less repetitive.
 
+Extra useful stuff:
+
+- [Attach a debugger to Timberborn](./attach-debugger): How to attach a debugger to Timberborn and debug the game code or your mods using DnSpy and Visual Studio.
+
 The following sections are more specific to certain types of mods that I made:
 
 1. [UI modding with TimberUi](./timber-ui): How to make UI mods for Timberborn using [TimberUi](../TimberUI).
 2. [Make a mod with Buff & Debuff mod](../BuffDebuff): Adding customizable buffs and debuffs to various in-game entities.
-3. [Make a mod with Scientific Projects mod](../ScientificProjects): Adding new research projects to the game.
+3. [Make a mod with Scientific Projects mod](../ScientificProjects): Adding new research projects to the game.
+4. [Make a code-less mod (using JSON) with Moddable prefab](../ModdablePrefab): Adding components to a prefab or changing their values using JSON (Blueprints) files.