How to Install Mods: Full Guide
Learn Casualties: Unknown how to install mods with BepInEx, correct plugin folders, loader checks, and a clean path to custom mods.
Casualties: Unknown how to install mods is one of those tasks that looks harder than it is — until you realize almost every working setup depends on the same loader. If you have ever downloaded a mod folder and wondered where it belongs, this guide gives you the install path, the folder layout, and the checks that prove the loader is running. Getting Casualties: Unknown how to install mods right matters because a misplaced file usually changes nothing in-game: the game starts clean, and your mod appears broken when it is simply in the wrong place.
Before touching any files, treat the install as two separate jobs: put the loader in the game folder, then put mods inside the loader's plugin folder. That order prevents most confusion. The steps below focus on manual installation because every mod you add later sits on top of the same loader path.
What You Need Before You Install Mods
Manual installs are simple, but they are not magic. You need the game installed through Steam, a file explorer, and BepInEx, the mod loader used for this game. If you already use the multiplayer mod or have installed any other mod, you can skip the loader setup and move directly to plugin placement. For a fresh setup, install BepInEx first, then return to the plugin steps below.
The cleanest approach to Casualties: Unknown how to install mods is to verify each prerequisite before you copy a single file.
| Requirement | Why it matters | Expected location |
|---|---|---|
| Casualties: Unknown game install | The loader must sit beside the game files | Your Steam library folder |
| BepInEx | Loads plugin files when the game starts | The game's root folder |
| Mod download | Supplies the content you want to add | Your Downloads folder first |
| BepInEx/plugins folder | The actual load point for mods | Inside the game folder |
| Tilde console | Helps confirm the loader is active | Opened with the tilde key in-game |
A few practical habits make the first install safer:
- Do not reinstall BepInEx if another mod or the multiplayer mod already works.
- Keep the original mod archive until the game loads successfully at least once.
- Move one new mod at a time when testing, especially after a failed launch.
- Keep each mod's folder structure intact instead of scattering loose files.
Casualties: Unknown How to Install Mods, Step by Step
The install sequence is short, but each step has a purpose. Skipping the folder check is the most common reason a mod seems dead on arrival.
-
Open the game folder through Steam. In your Steam library, open Casualties: Unknown, then use the option to browse local files. This opens the folder where the game executable and its support folders live.
-
Install BepInEx if you do not already have a working mod setup. The loader goes into the game's main folder. If the multiplayer mod or any other mod already works, you can skip this step because the loader is already present.
-
Confirm the plugin folder. Inside the game folder, locate
BepInExand thenplugins. That plugin folder is where normal mod files belong. If you cannot find it, your loader install is incomplete or in the wrong place. -
Copy the mod into the plugin folder. Open your downloaded mod, keep its folder structure intact, and move it into
BepInEx/plugins. For example, mods built around CU Core Library need CU CoreLib placed there as a dependency. -
Launch the game and check the console. Press the tilde key to open the in-game console and look for loader or plugin messages. A clean launch with no visible mod effect usually points back to a folder mistake.
| Step | Action | What success looks like |
|---|---|---|
| 1 | Browse local game files | You can see the game folder contents |
| 2 | Add BepInEx | The loader files sit in the game folder |
| 3 | Open BepInEx/plugins | The plugin folder exists and is accessible |
| 4 | Move the mod folder | The mod appears inside plugins |
| 5 | Launch and open the console | The game starts and the console responds |
Once the basic path is clear, Casualties: Unknown how to install mods becomes a repeatable routine: download, inspect the folder, copy to plugins, launch, and check the log.
Folder Layout: Where Each File Goes
Most failed mod installs are folder mistakes, not game bugs. The game folder contains BepInEx, and BepInEx contains plugins. That plugin folder is where ordinary mod files go. The Scav template and Visual Studio project are authoring files, so they belong in a documents or desktop project folder while you build, not inside the live plugin folder.
| Item | Put it here | Why |
|---|---|---|
| Game install | Steam library folder for Casualties: Unknown | Base game files |
| BepInEx loader | Game root folder | Starts the mod loader |
| Standard mod folder or DLL | BepInEx/plugins | The loader reads plugins from here |
| CU CoreLib | BepInEx/plugins | Dependency for mods built with CU Core Library |
| Scav template project | Desktop or Documents | Code project, not an in-game mod |
| Visual Studio project | Outside the live game folder | Keeps source files separate from installed mods |
If a mod download contains a folder named after the mod, treat that folder as the unit you move. If it contains a DLL and asset files, keep them together. The folder rule is also the fastest answer to most Casualties: Unknown how to install mods complaints: if the mod is not under BepInEx/plugins, the loader will not see it.
Test the Mod Loader Before Adding More Mods
Testing early saves time. The template test is useful because it gives a clear message: hello world. If you build the template and the console does not show that message, stop there. That message is the difference between a working loader and a setup error. Launch the game, press the tilde key, and read the console before you assume a mod is broken.
| Check | How to do it | Pass condition | If it fails |
|---|---|---|---|
| Launch the game | Start Casualties: Unknown normally | The game reaches the world | Recheck the loader install |
| Open the console | Press the tilde key | The console appears | Verify BepInEx is installed |
| Run the template test | Build and test the Scav template | The log shows hello world | Stop and fix the dependency or build |
| Confirm mod placement | Open BepInEx/plugins | The desired mod folder is present | Move the mod into the plugin folder |
A successful test does not guarantee every mod will work, but it confirms the Casualties: Unknown how to install mods foundation is correct. That is why the template check is worth doing before you pile on several downloads at once.
Build Your Own Mod After the Install
If you want to move from installing to authoring, the workflow continues from the same loader. You install Git, use a terminal command to place the Scav template on your computer, open that template in Visual Studio with C# support, and add CU CoreLib as a dependency. Then build the solution and test for hello world before adding custom assets.
| Authoring stage | Tool or file | Purpose |
|---|---|---|
| Project download | Git | Places the Scav template on your machine |
| Code work | Visual Studio with C# | Edit and build the template |
| Dependency | CU CoreLib | Supports item, liquid, recipe, and building APIs |
| Assets | Sprites and images | Added to the project as embedded resources |
| Test | Tilde console | Confirms the template prints hello world |
From there, the same workflow can register a custom mushroom, add a liquid such as hydrochloric acid, create crafting recipes, and set up an acid mushroom colony that uses standard generation and drops the mushroom. Those are examples of what the CU Core Library route supports, not requirements for a first install. Think of Casualties: Unknown how to install mods as the entry point; authoring is the optional second layer.
Troubleshooting and FAQ
| Symptom | Likely cause | Fix |
|---|---|---|
| Game starts, but the mod does nothing | Files are not in the plugin folder | Move the mod folder into BepInEx/plugins |
| The loader seems missing | BepInEx is absent or in the wrong folder | Reinstall it in the game folder, unless another mod already works |
The template never shows hello world | Dependency or build issue | Stop and correct the CU CoreLib reference or build |
| A CU-based mod is missing content | CU CoreLib is absent | Place CU CoreLib in BepInEx/plugins |
| The console does not open | The loader is inactive or the tilde key was not used | Launch the game and press the tilde key |
What is the first requirement for Casualties: Unknown how to install mods?
The first requirement is a working BepInEx setup in the game folder. If you already have the multiplayer mod or another working mod, the loader is already present and you can go straight to BepInEx/plugins.
Where do mod files go?
Ordinary mod files go inside BepInEx/plugins in the Casualties: Unknown game folder. Authoring files such as the Scav template belong in a desktop or documents project folder instead.
How can I confirm the loader is working?
Launch the game, press the tilde key, and check the console. When testing the Scav template, the expected result is the hello world message.
Can I create mods after learning Casualties: Unknown how to install mods?
Yes. The authoring path uses Git, the Scav template, Visual Studio with C#, and CU CoreLib as a dependency. Build the template and confirm hello world before adding custom items, liquids, recipes, or world generation.
Related Guides
Best Quality of Life Mods
Find a Casualties: Unknown quality of life mod for saves, UI, wearables, and stability, with install tips and compatibility checks.
Casualties: Unknown Mods Guide
Build custom items, liquids, recipes, and spawns for Casualties: Unknown mods, plus install BepInEx, set up CU Library, and pick practical mods.
Multiplayer Mod: Setup Guide
Install the Casualties: Unknown multiplayer mod with BepInEx, then use Steam lobbies, voice chat, revives, and shared warmth in co-op.
Save Mod: Save Anywhere Guide
Learn how the Casualties: Unknown save mod works, when to use save anywhere, and how to avoid achievement and mod conflicts.