Port Custom Maps to GoreBox

Custom maps extend GoreBox far beyond default Legacy and Pillars playgrounds — community authors build warehouses, horror corridors, race tracks, and boss arenas through the Map Editor and export to mod.io. Porting a map means subscribing to the map addon plus every dependency, enabling all packs, and fixing navigation so GoreDolls and players interact correctly with imported geometry. This guide and video walkthrough cover the full pipeline from Workshop subscription to playable session.

Map porting differs from simply loading default maps. Workshop exports bundle MAPCG data, texture references, embedded spawners, and optional Lua scripts. Missing any dependency produces empty voids, pink missing textures, or instant crashes. Read map descriptions carefully before subscribing.

Port custom maps searches usually mean you found a Workshop arena on YouTube or Discord and need it running locally tonight. Follow dependency subscription before troubleshooting performance — nine of ten failed ports are missing vehicle or texture packs listed in small print below the map title.

Find the target map on mod.io through the in-game browser or web hub. Subscribe to the map addon first, then subscribe to every linked dependency — custom props, vehicles, GoreDoll skins, and sound packs. Our mod.io download guide covers subscription mechanics on PC; Android users download ZIPs and extract via ZArchiver.

Enable all related addons in the Addons manager before launching. Restart GoreBox after subscribing to large packs so the map list rebuilds. Maps appear under custom or Workshop categories depending on author tagging. Wait for download progress bars to complete before launching — partial downloads cause the most confusing empty-map bugs for first-time porters.

Select the ported map from the menu and load in Creator Mode for unrestricted testing. Walk the full perimeter checking for fall-through geometry, invisible walls, and missing textures. Spawn GoreDolls to verify AI pathing — if NPCs spin or walk into obstacles, run /navgenerate after confirming static props are frozen correctly.

Use Reality Crusher Phase mode to inspect interior props clipped inside walls. /freecam helps document bugs to report to map authors on mod.io comments. For race maps, test vehicle spawn points with multiple models to confirm collision mesh alignment. Walk the full map boundary twice — many port failures are single missing wall segments at far map edges.

Large ported maps may stutter on mid-tier PCs when combined with heavy addon prop counts. Lower spawn density during first playthroughs, disable unrelated GoreDoll packs, and close background applications before loading 4K-textured arenas. Android players should test ported maps on Wi-Fi first — cellular downloads of multi-hundred-megabyte dependency chains fail frequently.

Report performance data to map authors with GPU model and FPS estimates. Constructive benchmarks help authors bake LOD-friendly props in Map Editor revisions without guessing hardware limits across the player base. Screenshot missing texture examples when reporting dependency issues — authors fix faster with visual proof than vague crash reports alone.

Authors porting their own Map Editor exports should bundle clear dependency lists and navmesh instructions in mod.io descriptions. Include screenshots at day and night lighting if applicable. Tag maps with game version v16 to filter incompatible subscribers.

Learn Map Editor fundamentals on our map editor basics guide before publishing. Advanced builders reference Map Editor documentation and custom maps overview for export settings. Lua-heavy maps should link to Lua modding resources for script maintainers.

When porting maps authored for older GoreBox versions, check mod.io comments for community patch forks before attempting manual geometry fixes. Some legacy arenas require prop swaps because texture IDs changed between major releases. Credit original authors when uploading compatibility forks and link dependency addons explicitly so new players avoid the trial-and-error subscription loop.