Biografía

When Burglin' Gnomes mods fail, the cause is usually not mysterious. There are a few typical errors: BepInEx not loading, MelonLoader conflicts, files placed in the wrong directory, missing generated folders, unmet requirements, and Linux or Steam Deck launch configuration issues under Proton.

Because the Burglin' Gnomes mod scene is still centered primarily around BepInEx 5, troubleshooting should begin with the loader rather than with individual mods. A broken loader means every mod layered on top of it will appear broken as well. The site’s BepInEx page identifies version 5.4.2304 as a tested stable version for the game and repeats the expected structure: install BepInEx in the game root folder, run the game once, allow it to generate folders, and then place downloaded mod files into BepInExplugins.

Start With the Basic Checks

Before diagnosing any specific mod, confirm the following:

• BepInEx 5 is installed in the root game directory.
• You launched the game once after installing BepInEx.
• The game created the BepInEx, plugins, and config folders.
• The mod files were placed in BepInExplugins.
• The mod’s page lists BepInEx 5 as its requirement.

If one of those conditions is missing, you do not yet have a reliable mod environment. Do not continue installing more mods until that base state is correct.

Problem 1: BepInEx Does Not Load at All

This is the most common failure point. BepInEx does not work because MelonLoader is installed in the same game folder. The troubleshooting section also explains why: MelonLoader is another Unity mod loader, and some mods are specifically built for it. Running both loaders together for the same game creates a conflict.

A similar warning appears on the BepInEx page itself: if MelonLoader is installed, remove it, because both loaders cannot be installed for the same game at the same time. Comments on that page reinforce the same conclusion, including a March 2026 exchange where a user reported that BepInEx started working only after fully uninstalling MelonLoader, and the site owner confirmed that both loaders cannot be installed simultaneously.

Fix

Remove MelonLoader completely before reinstalling or retesting BepInEx.

You can select one of two methods:

Option 1: Run MelonLoader.Installer.exe and choose Uninstall.
Option 2: Manually delete the MelonLoader, userdata, and mods folders from the game root, then delete version.dll and dobby.dll. The guide notes that backing up the mods folder before deletion may be useful.

After that, launch the game without MelonLoader present, then install BepInEx again in a clean state.

Problem 2: No Plugins Folder or Config Files Appear

If BepInEx was copied into the game folder but no plugins or config folders appear after launch, the installation did not initialize properly. According to the BepInEx page, running the game once after extraction should generate the required configuration files and the plugins folder automatically.

Fix

Verify that BepInEx was extracted into the root game directory, not into a subfolder or archive folder copy. The BepInEx page describes the root folder as the location where the game executable resides. Then launch the game once and wait for BepInEx to initialize. If the folders still do not appear, return to Problem 1 and check for an existing MelonLoader installation or leftover files.

Problem 3: The Mod Is Installed but Nothing Happens

If the loader works and the folder structure is correct, the next most common issue is that the mod is present but the user is not triggering it correctly or is expecting visible behavior immediately.

Several current mods have explicit activation methods:

• Spawn Menu opens with Insert and closes with Esc or Insert.
• Chat Mod opens with Enter and sends with Enter again.
• Fly Mod uses F to toggle flight mode.
• Item Highlight Mod uses F4 to highlight useful items.
• Mod Config Manager adds a MOD CONFIG button in the main menu.

Fix

Check whether the mod requires a hotkey, menu button, or specific in-game state to become visible. Then check the corresponding .cfg file in BepInExconfig, because the site’s install guide states that configuration files are generated after the game runs with a mod installed, and those files can be edited to change settings such as keybinds.

Problem 4: The Mod Files Are in the Wrong Folder

Download the archive and unzip it into Burglin’ Gnomes DemoBepInExplugins. This applies to pages such as Spawn Menu, Chat Mod, More Players Mod, and LOBBY LIST Mod.

Fix

Open the archive again and verify where its files were placed. Most mods are expected to sit inside BepInExplugins. If a mod came with a folder and additional files, keep that structure intact when moving it into the plugins directory. Do not place BepInEx mods directly in the game root unless the mod page explicitly instructs you to do so.

Problem 5: The Mod Needs a Requirement You Skipped

The site’s general install guide explicitly tells users to read the Requirements section before installation. For many current Burglin' Gnomes mods, the requirement is BepInEx 5, but that still needs to be verified mod by mod. Spawn Menu, Chat Mod, More Players Mod, and LOBBY LIST Mod all explicitly list BepInEx 5 as their requirement.

Fix

Reopen the specific mod page and confirm all listed requirements. If the loader requirement is not satisfied, reinstall the loader cleanly before doing anything else. If the mod expects configuration support or another utility component, install those as instructed on the page.

Problem 6: Multiplayer Mods “Work” but Not for Everyone

Some multiplayer-focused mods require more than one player to have the same setup. Chat Mod is a clear example: its page states that messages are delivered to all players who have the mod installed. The LOBBY LIST Mod page also recommends Chat Mod specifically because not everyone uses a microphone, but notes that both players need Chat Mod installed to send and receive messages.

Fix

When testing multiplayer utilities, confirm that all relevant players have installed the same mod and the correct requirement chain. Do not assume a host-only install will provide all functionality to the rest of the lobby if the mod page says otherwise.

Problem 7: The Game Becomes Unstable After Changing Limits

Not every failure is an installation failure. Sometimes the mod loads correctly, but the chosen settings are too aggressive. The More Players Mod page is a good example. It says the default maximum is set to 10, but the config can be changed to much higher values, even 100. The page also warns that setting the value too high can cause significant bugs, network lag, and general instability.

Fix

Return the mod to a conservative configuration value, then test again. If a problem only appears after raising limits, assume instability is a settings issue rather than a failed install. This is especially relevant for multiplayer and sandbox-heavy setups.

Problem 8: Linux or Steam Deck Setup Fails Under Proton

winhttp.dll does not load automatically under Proton. Without the correct launch option, BepInEx may fail to initialize even if the files were copied correctly.

Fix

Set the Steam launch option exactly as shown in the site’s install guide:

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

The guide says this forces Steam and Proton to use the modded winhttp.dll instead of the built-in Windows version. On Linux and Steam Deck, this should be treated as part of the normal setup rather than as an optional tweak.

Problem 9: You Need a Clean Reset

When multiple mods, loaders, and old files have been mixed together, a clean reset is often faster than selective repair.

To remove MelonLoader, delete the MelonLoader, userdata, and mods folders plus version.dll and dobby.dll, or use its installer’s uninstall option.

To remove BepInEx, delete the BepInEx folder, .doorstop_version, doorstop_config, and winhttp.dll from the game directory.

Fix

Remove the old loader completely, confirm the game launches cleanly, then rebuild the setup in this order:

1. Install BepInEx 5 in the root folder.
2. Launch the game once.
3. Confirm that plugins and config were generated.
4. Install one mod only.
5. Test that mod before adding anything else.

Wrappin' Up

Most Burglin' Gnomes mod failures come from a short list of repeatable issues, and the biggest one is the loader conflict between BepInEx and MelonLoader. After that, the most likely causes are misplaced files, skipped requirements, missing generated folders, or platform-specific setup mistakes on Proton-based systems.

The fastest route to a stable setup is disciplined troubleshooting: verify the loader first, confirm the folder structure, test one mod at a time, and only then move into more complex multiplayer or sandbox configurations. In practice, that solves most problems before they become complicated.