How to Fix BepInEx Not Working or Crashing in Gorilla Tag

Introduction: Why Does BepInEx Stop Working?

When modding Gorilla Tag on PC VR, BepInEx is the foundation that loads every custom .dll plugin. If BepInEx fails, none of your mods—from custom maps to recording cameras—will appear in-game.

Common symptoms of a broken BepInEx installation include:

• Gorilla Tag closes immediately upon clicking “Play” on Steam.
• The VR headset gets stuck indefinitely on a black screen.
• The game launches normally, but none of your mods load in the treehouse.
• Steam displays an error: “Executable or dynamic link library failed to initialize.”

This technical guide walks through the exact diagnostic steps to fix BepInEx and get your mod setup running smoothly.

Step 1: Enable the BepInEx Console Window

The single most effective way to debug BepInEx is to enable its live diagnostic console window. This displays real-time loading logs on your desktop monitor when the game starts:

1. Open your Gorilla Tag installation directory:

   C:\Program Files (x86)\Steam\steamapps\common\Gorilla Tag\BepInEx\config\

2. Locate the file named BepInEx.cfg and open it with Notepad.
3. Press Ctrl + F and search for [Logging.Console].
4. Change the setting:

   # Before:
   Enabled = false
   
   # After:
   Enabled = true

5. Save the file and launch Gorilla Tag through Steam. A black terminal window will now open alongside the game. Look for RED text blocks—they will name the exact plugin causing your crash.

Step 2: Fix the Missing winhttp.dll / Doorstop Error

BepInEx relies on Unity Doorstop to intercept the game’s startup sequence. If Doorstop files are missing or placed in the wrong folder, BepInEx will simply never trigger:

Verify that your main Gorilla Tag folder contains these three files in the root folder (next to Gorilla Tag.exe):

1. winhttp.dll (The Windows hook that forces Unity to load BepInEx)
2. doorstop_config.ini (The initialization file)
3. BepInEx (The folder containing core, config, and plugins)

If winhttp.dll is missing, download a clean copy of BepInEx 5.4.21 (x64) and extract the zip archive directly into your main game directory.

Step 3: Check for 32-Bit vs. 64-Bit Mismatch

Gorilla Tag is a 64-bit Unity executable. A very common mistake is accidentally downloading the 32-bit (x86) version of BepInEx:

• Incorrect: BepInEx_x86_5.4.21.0.zip (Will crash on startup with a memory violation).
• Correct: BepInEx_x64_5.4.21.0.zip (64-bit release).

If you suspect you installed the wrong build, delete the BepInEx folder and winhttp.dll, then reinstall the 64-bit package.

Step 4: Isolate Corrupted or Outdated Plugins

Whenever Another Axiom releases an official Gorilla Tag update, older mods will reference obsolete Unity functions, causing a crash loop.

Use the Binary Split Method to identify the culprit:

1. Navigate to Gorilla Tag\BepInEx\plugins\.
2. Create a temporary folder on your desktop named ModBackup.
3. Move all plugins except Utilla.dll out of the plugins folder into ModBackup.
4. Launch Gorilla Tag.
   • If the game launches cleanly, BepInEx itself is working, and one of your other plugins was causing the crash.
5. Move your plugins back into plugins/ one by one, testing the game after each addition until you find the exact file that triggers the crash.

Step 5: Perform a Clean Game Verification

If all else fails, verify your base game files through Steam to repair any corrupted vanilla assets:

1. Open Steam and go to your Library.
2. Right-click Gorilla Tag > select Properties.
3. Click the Installed Files tab > select Verify integrity of game files.
4. Steam will scan and redownload any missing or corrupted base game files.
5. Reinstall BepInEx 64-bit fresh.

Summary Checklist

• BepInEx 64-bit (x64) is installed, not 32-bit.
• winhttp.dll is sitting in the root folder alongside Gorilla Tag.exe.
• Outdated plugins from previous game patches are removed from BepInEx/plugins/.
• Antivirus / Windows Defender has not quarantined winhttp.dll.