GoreBox Mod Installation on PC

While mod.io Workshop handles most GoreBox v16 addon installs automatically, manual folder placement remains essential for Lua developers testing unpublished scripts, recovering broken sync states, and installing community zips shared outside the Workshop browser. Every manually installed addon lives in a dedicated Mods directory that GoreBox scans on startup. Understanding this path prevents the classic "mod not loading" frustration when folders are nested one level too deep.

On Windows, the default mod path is:

C:Users<YourUsername>AppDataLocalLowF2GamesGoreBoxMods

Replace <YourUsername> with your Windows account name. The AppData folder is hidden by default — paste the path into File Explorer's address bar or enable "Hidden items" in the View tab. Each addon should be its own subfolder inside Mods containing Lua entry scripts, manifest files, and asset bundles per the structure defined at gorebox-modding.github.io. Our Lua modding guide walks through required files.

Download or extract the addon zip from mod.io, Discord, or your own MAPCG export pipeline. Create a new folder inside Mods named after the addon — for example MyCustomGoreDolls. Copy all extracted files into that folder without an extra nested directory layer. A common mistake is placing files in ModsMyAddonMyAddon which breaks load paths.

Launch GoreBox, enable Creator Mode from the menu before loading a map, and verify the addon loaded via spawn menu new categories or /openConsole developer logs. If nothing appears, cross-check script entry points against the current API — outdated require paths fail silently on older community packs. Compare against working examples from our Workshop guide and the mod.io tutorial.

When testing map addons, load them from the map selection screen after confirming the addon registers custom MAPCG entries. Port workflows from our port custom maps guide if importing legacy formats.

Steam Deck and Linux desktop builds mirror the same F2Games folder structure under the Unity persistent data path. Typically:

~/.config/unity3d/F2Games/GoreBox/Mods on Linux, or the equivalent under ~/.local/share depending on your Proton or native build — verify by searching for an existing GoreBox config file after running the game once.

macOS stores the path under:

~/Library/Application Support/F2Games/GoreBox/Mods

Installation steps match Windows: one subfolder per addon, flat file structure, restart the game. Proton users on Steam Deck should exit the game completely before copying files so Linux filesystem caches refresh. Pair manual installs with Creator Mode noclip from our Creator Mode controls page to quickly scout test maps.

Backup your Mods folder before bulk experiments — symlink accidents and half-finished script edits are easier to revert with a zip archive.

Steam Cloud does not sync the Mods folder — treat local copies as authoritative and re-download from mod.io when rebuilding a fresh PC install. Keep a text manifest listing subscribed addon names so you can batch re-subscribe after OS reinstalls without guessing from empty spawn menus.

If an addon fails after a GoreBox patch, delete its folder from Mods and re-subscribe through mod.io to fetch an updated build. Stale DLL or Lua files from pre-v16 eras must never mix with v16 API scripts — they crash the load pipeline or spawn invisible entities. Use /openConsole after enabling Creator Mode; error strings usually cite line numbers in your Lua entry file.

Conflicts occur when two addons register the same spawn ID — disable one folder by renaming it outside Mods temporarily. Command-line enthusiasts cross-reference console permissions on our all commands list when addons expose custom / commands.

For Android parity testing, copy stable builds to the device path in our Android installation guide using ADB or cloud storage — keep PC and mobile folder structures identical to reduce author support burden.