Biografía

Installing mods for Burglin' Gnomes is fairly straightforward once the base setup is in place. The current mod ecosystem is centered primarily around BepInEx 5, and the site’s installation guide describes a consistent process used across many mod pages: install BepInEx first, launch the game once so required folders are generated, then place mod files inside the BepInExplugins folder. The same pattern is repeated on pages for mods such as More Players Mod, Chat Mod, Spawn Menu, Inventory Expander, and Mod Config Manager.

The important part is not speed but accuracy. Most installation issues do not come from the mods themselves. They usually happen because the wrong loader is installed, files are placed in the wrong folder, a required dependency is missing, or an older setup is still sitting in the game directory. The good news is that these problems are predictable and easy to avoid with a clean installation routine.

Before You Install Anything

Before adding your first mod, open the game’s local files through Steam and identify the root game folder. You can reach it by right-clicking the game in Steam, selecting Manage, and then choosing Browse local files. This is the folder where BepInEx must be extracted.

It is also worth understanding one basic rule up front: many Burglin' Gnomes mods are distributed as .dll files, and some come with extra folders or supporting files. According to the burglingnomesmods.com’s installation guide, these should be moved into the BepInExplugins directory after BepInEx has created it. If a mod page lists additional requirements, those must be installed too.

Step 1: Install BepInEx 5

BepInEx 5.4.2304 is a tested stable version for Burglin' Gnomes, and the site’s install guide says BepInEx is required to enable mods in the game.

The installation sequence is simple:

1. Download BepInEx 5 Stable.
2. Open the archive.
3. Drag all contents directly into the Burglin' Gnomes game folder.
4. Launch the game once.
5. Wait until the main menu appears, then close the game.

After that first launch, BepInEx should generate the folders you need, including plugins and config. The site also notes that a console window should appear alongside the game during this process, which is a useful sign that BepInEx is loading correctly.

Step 2: Confirm That BepInEx Generated the Correct Folders

After the first successful launch, check the game folder and make sure the following structure now exists:

• BepInEx
• BepInExplugins
• BepInExconfig

These folders are created after BepInEx runs for the first time. If they do not appear, stop there and fix the loader installation before adding any mods. Installing mods before the base folders exist is one of the fastest ways to create confusion later.

Step 3: Install a Mod the Correct Way

Once BepInEx is working, most Burglin' Gnomes mods follow the same basic installation pattern. The site’s guide says to download the mod, review the Requirements section, and then move the mod’s .dll file into BepInExplugins. If the archive includes an additional folder or extra files, those should also be placed in the plugins directory rather than separated from the main mod file.

That same instruction is repeated on current mod pages. For example, More Players Mod, Chat Mod, Spawn Menu, Inventory Expander, Hands Color Mod, Feet Color Mod, and Timeout Fix all state that you should first make sure BepInEx 5 is installed and then unzip the archive into Burglin’ Gnomes DemoBepInExplugins.

In practical terms, that means your workflow should look like this:

1. Download one mod archive.
2. Open it and inspect the contents.
3. Read the Requirements section on the mod page.
4. Move the included files into BepInExplugins.
5. Launch the game and verify that the mod loads.

Do not install five or six mods at once on your first attempt. Install one, confirm it works, and only then move to the next. That approach makes troubleshooting much easier if something goes wrong.

Step 4: Check for Dependencies Before Launching

A large share of “broken mod” reports are actually dependency problems. Check the Requirements section before installing a mod. In many cases, the requirement is simply BepInEx 5, but some tools and framework-related additions may expect other support files or a particular setup order.

This is especially important with utility mods. For example, Mod Config Manager requires BepInEx 5 and is installed inside the plugins folder like other BepInEx-based mods. Once it is running, it adds an in-game configuration interface rather than requiring manual edits to config files for every change.

Step 5: Launch the Game and Test One Mod at a Time

After installation, launch Burglin' Gnomes and confirm that the mod is actually active. A few mods provide easy in-game checks:

• Spawn Menu can be opened with the Insert key.
• Item Highlight Mod uses F4 to highlight items that can be added to your inventory.
• Fly Mod uses F to toggle flight mode.
• Mod Config Manager adds a MOD CONFIG button to the main menu.

These kinds of visible checks matter because they tell you whether the problem is “mod not installed” or simply “mod installed but I have not triggered it yet.” Test one mod, confirm its hotkey or menu entry works, then continue with the next install.

Step 6: Edit Configuration Files Only After First Launch

The install guide states that once you run the game with a mod installed, a .cfg file will usually appear in BepInExconfig. Those configuration files can be opened in a text editor such as Notepad to change settings, including hotkeys.

This is another reason not to panic if a mod does not immediately behave exactly the way you expected. Some mods need a first launch to generate their config file, and some are easier to manage once that config exists. If you prefer not to edit text files manually, Mod Config Manager can simplify the process by moving compatible settings into an in-game menu.

The Most Common Installation Mistakes

One issue stands out above all others: BepInEx often fails because MelonLoader is installed. The site states that in “99.99% of cases,” BepInEx does not work because MelonLoader is present in the same game folder. It also explains that MelonLoader is another Unity mod loader and that some mods are built specifically for it, which means mixed setups can create direct conflicts.

Other common mistakes are simpler:

• placing the .dll in the wrong folder,
• skipping the first BepInEx launch,
• ignoring the Requirements section,
• installing too many mods at once,
• assuming every mod uses the same loader without checking.

The safest approach is to treat mod installation as a controlled process rather than a bulk file dump.

How to Remove MelonLoader If It Is Causing Problems

There are two ways to remove MelonLoader if it is interfering with BepInEx.

Option 1: Use MelonLoader.Installer.exe and select Uninstall.
Option 2: Remove it manually by deleting the MelonLoader, userdata, and mods folders, then deleting the version.dll and dobby.dll files from the game’s root directory. The guide notes that you may want to back up the mods folder before deleting it.

If you have ever experimented with multiple loaders, this cleanup step should happen before any serious troubleshooting. Otherwise you may spend time diagnosing the wrong issue.

Linux and Steam Deck Special Case

A specific note for Linux and Steam Deck users. Because winhttp.dll does not load automatically under Proton, the guide says you must add a launch option in Steam so the game uses the native modded DLL. The exact launch option provided is:

WINEDLLOVERRIDES="winhttp=n,b" %command%

The guide explains that this forces Steam/Proton to use the modded winhttp.dll instead of the built-in Windows version. For Linux and Steam Deck players, this is not an optional refinement; it is part of getting BepInEx to load correctly in the first place.

How to Uninstall a Mod

Uninstalling a standard Burglin' Gnomes mod is straightforward. The site’s install guide says to delete the mod’s .dll and any associated files or folders from BepInExplugins. If the mod also created a configuration file and you want a full cleanup, removing the related .cfg file from BepInExconfig is also a sensible housekeeping step, though the guide specifically highlights the plugin files as the essential removal target.

How to Uninstall BepInEx Completely

If you want to return the game to an unmodded state, delete the following from the game folder:

• the BepInEx folder,
• .doorstop_version,
• doorstop_config,
• winhttp.dll.

That removes the loader and its supporting files from the installation. If you are troubleshooting a badly broken setup, a full clean reinstall of BepInEx after removing these files is often more efficient than patching a messy folder structure.

Final Notes

The current Burglin' Gnomes installation process is not difficult, but it does reward careful setup. The pattern across the site is very consistent: install BepInEx 5, run the game once, place mod files into BepInExplugins, verify requirements, then test each mod individually. Utility tools such as Mod Config Manager can make the process easier once your base setup is working, but they do not replace the need for a clean initial installation.

The simplest way to avoid problems is to stay disciplined: one loader, one clean folder structure, one mod at a time. In a young mod scene, that approach will save more time than any shortcut.