GoreBox Workshop & mod.io

GoreBox v16 replaced the fragmented legacy mod scene with a unified Addons system powered by mod.io Workshop integration. Instead of manually hunting forum download links, players browse curated addon pages, subscribe with one click, and sync content directly inside the game. Maps, custom GoreDolls, weapon packs, vehicles, and Lua scripts all flow through the same pipeline — a major quality-of-life upgrade for sandbox creators and players migrating from pre-v16 builds.

Open the in-game Workshop or Addons menu from the main GoreBox interface. The mod.io browser lists trending submissions, new releases, and categories filtered by content type. Each addon page shows screenshots, author notes, compatibility tags, and subscriber counts. Subscribing adds the addon to your library; GoreBox downloads files on next launch or when you press the sync button depending on your build. Our video walkthrough on the download mods via mod.io guide demonstrates the full subscribe-and-play workflow step by step.

When you find an addon worth installing — perhaps a custom arena for Verse Curse practice or a GoreDoll pack from our custom GoreDolls tutorial — click Subscribe on the mod.io page inside GoreBox or on the mod.io website linked to your account. Linked accounts keep subscriptions synchronized across devices where GoreBox is installed. Unsubscribe from the same interface to remove future updates; locally cached files may remain until you clear them manually via PC or Android paths documented in our PC install guide and Android install guide.

After subscribing, return to the main menu and allow the game to finish downloading. Spawn menus gain new categories when Lua addons register entities correctly — if items fail to appear, open the developer panel with /openConsole after enabling Creator Mode and check for load errors. Broken addons usually trace to outdated API calls; authors should reference the current documentation at gorebox-modding.github.io covered on our Lua modding page.

Organize large subscription lists by unsubscribing from unused content — stale addons slow load times and clutter spawn wheels on both PC and mobile.

Workshop addons fall into several community categories. Custom maps export from the MAPCG Map Editor — learn publishing basics in our Map Editor basics guide and port custom maps tutorial. GoreDoll and texture packs replace body meshes, hair, and clothing for machinima characters. Weapon and vehicle packs extend the arsenal beyond vanilla items listed in our weapons catalog.

Lua script addons implement gameplay logic — infection modes, economy systems, custom boss triggers — using the official GoreBox Modding API. Script addons require v16 and may depend on other subscribed packages; read dependency notes on each mod.io listing before subscribing. Combine Workshop maps with Reality Crusher builds from our Reality Crusher guide for hybrid sandbox experiences impossible in vanilla maps alone.

Always verify an addon's last update date after major GoreBox patches. F²Games API changes can silently break unmaintained scripts until authors publish fixes.

mod.io is the recommended installation path for most players because it handles updates, dependency resolution, and integrity checks automatically. Manual installation remains necessary when testing unpublished addons during development, sideloading community zips shared on Discord, or recovering files when mod.io sync fails. Developers drop test builds into the Mods folder at AppData/LocalLow/F2Games/GoreBox/Mods on Windows — exact steps on our PC installation page.

Android players can subscribe through mod.io when the in-game browser works on their build, or sideload with ZArchiver into the Android data path explained in our Android mods installation guide. Never mix conflicting duplicate addons with identical spawn registrations — last-loaded scripts win and produce confusing bugs.

Report broken Workshop listings to mod.io moderation and notify authors on linked Discord servers. The GoreBox community moves faster when players share reproducible steps alongside /openConsole log snippets.