GoreBox Custom Maps & Workshop

Custom maps extend GoreBox beyond Legacy and Pillars — community arenas, race tracks, roleplay districts, and boss practice chambers distributed through the official mod.io Workshop integration added in the v16 addons era. F²Games routes map discovery, subscribe-unsubscribe flow, and automatic updates through mod.io rather than legacy third-party sites, though porting from older file shares remains common among veteran creators migrating pre-Workshop archives.

Whether you subscribe to a trending PvP box or upload your first MAPCG export, custom maps load from the same map select screen as official content. Installed Workshop entries appear alongside local imports. Creator Mode, Reality Crusher, Lua addons, and console commands behave identically — but authors must validate navmesh, spawn points, and mobile performance because Workshop quality varies wildly.

Disk space matters on budget laptops — each subscribed map caches locally. Unsubscribe from unused entries quarterly. Steam and Android mod.io clients share the same backend but may sync on different schedules; if a friend sees your upload before you do, force-close and relaunch the Workshop browser.

Open GoreBox's Workshop browser from the main menu or addons panel — exact labeling varies slightly by platform but consistently points to mod.io backend services. Browse categories: maps, addons, weapons, and total conversions. Subscribe to a map; the client downloads packaged files to your local library and keeps them updated when authors publish revisions. Unsubscribe to reclaim disk space on lower-end drives.

Before publishing your own creation, finish the MAPCG editor export pipeline and playtest with /navgenerate, GoreDoll hordes, and optional /divine boundary checks. Upload screenshots and descriptive titles — Workshop discovery favors clear keywords like "snipers," "boss arena," or "parkour." Follow F²Games moderation rules: no stolen assets, no misleading thumbnails, and stable builds that do not crash on load.

Porting refers to adapting maps from older GoreBox builds, friend-shared files, or foreign sandbox formats into v16-compatible packages. Start by identifying the source format: native MAPCG exports load cleanly; legacy archives may need cube rebuilds or texture reassignment. Never assume pre-v16 navmesh data transfers — rerun /navgenerate on every port.

Common porting steps: import geometry, rebuild spawn entities, validate Reality Crusher interaction surfaces, test explosive chain reactions for unintended lag spikes, and compare player jump heights against official Legacy benchmarks. If a port originates from another player's unpublished file, obtain permission before Workshop re-upload. Document credit in descriptions — the community enforces attribution aggressively.

Batch porting old archives? Maintain a checklist spreadsheet: source filename, target GoreBox version, navmesh pass date, and known broken spawn IDs. Ports fail silently when spawn entity names changed between builds — compare against a fresh MAPCG New Project reference file.

Custom maps frequently host addon weapons, Lua scripted events, and player-designed boss encounters unrelated to Observer, Verse Curse, or Phil. Separate official progression — blueprint hunts on Legacy, Mighty skin rewards, Toolgun craft restrictions — from sandbox-only Workshop arenas where hosts enable /give Toolgun freely. Label your map accurately so players do not expect canonical boss triggers on a pure deathmatch box.

For creators aiming at structured encounters, study official design: Legacy's lake pipes for hidden bosses, Pillars' clock landmarks for orientation, and inventory rules from our Phil fight guide when scripting Toolgun-limited arenas. Link players to console basics if your map README requires host commands. Strong custom maps combine polished geometry, honest descriptions, and post-export technical passes — navmesh, lighting, and performance — that distinguish professional Workshop entries from greybox tests.

Version mismatches break ports silently — always label which GoreBox build you tested against in Workshop descriptions. Subscribers on older Android builds may crash on v16-only Lua hooks; provide fallback builds or clear minimum version notes. Cross-platform testing on Steam and mobile catches aspect ratio issues early before negative reviews accumulate.