GoreBox Mod Installation on Android

Android GoreBox supports the same v16 Addons ecosystem as PC through mod.io subscriptions and manual sideloading. Mobile players who prefer Discord-shared zips, beta tester builds, or offline installs rely on ZArchiver — a free file manager with robust zip extraction — to place addon folders in GoreBox's protected Android data directory. This guide covers the full ZArchiver workflow, exact path conventions, permission pitfalls on modern Android versions, and when to prefer in-game mod.io sync from our mod.io download guide.

Before sideloading, install GoreBox from your official store source and launch once so Android creates the base data folders. Enable Creator Mode from the menu when testing new addons — mobile Creator toggles mirror desktop permissions for spawn limits and debugging. Touch controls differ from PC — review our mobile controls guide before testing vehicle or weapon addons designed for keyboard input.

Install ZArchiver from a trusted app store. Download the addon zip to your device — from mod.io's mobile site, a Discord attachment, or transferred from PC. Open ZArchiver, navigate to Downloads, and extract the zip. Verify the extracted folder contains Lua scripts, manifest files, and asset subdirectories matching the structure in our Lua modding reference — not a single nested duplicate folder.

Move or copy the addon folder into GoreBox's Mods directory inside Android scoped storage:

Android/data/com.F2Games.GoreBox/files/Mods/

Package names may vary slightly by store build — if the path differs, search ZArchiver for an existing Mods folder after launching GoreBox once. Place each addon as Mods/AddonName/ parallel to siblings, identical to the PC layout at AppData/LocalLow/F2Games/GoreBox/Mods covered in our PC install guide.

Force-stop GoreBox from Android settings, relaunch, enable Creator Mode, and load Legacy or a lightweight map to test spawns before importing heavy Workshop arenas.

Android 11 and newer restrict direct file access to Android/data unless the file manager requests "All files access" or uses the system document picker. ZArchiver prompts for storage permissions on first launch — grant them or extraction silently fails into inaccessible cache directories. Samsung and Xiaomi devices add vendor-specific battery optimizations that kill GoreBox mid-sync; disable aggressive background limits for both GoreBox and ZArchiver when downloading large mod.io packages.

When mod.io in-game sync works on your device, prefer it over manual sideloading — updates arrive automatically and reduce path errors. Manual installs remain necessary for addons not yet published to Workshop or shared privately in beta communities. Cross-reference our Android mods installation tutorial for video steps if text paths confuse first-time sideloaders.

Never install addons from unverified sources — Lua scripts execute with game privileges. Stick to mod.io listings and trusted community authors linked from the F²Games Discord.

Addon missing from spawn menus after sideloading usually means incorrect folder depth or a typo in the package path. Re-open ZArchiver, confirm files sit directly under Mods/YourAddon/, and delete duplicate nested copies. Check /openConsole on builds that expose limited console access, or watch for in-game error toasts after enabling Creator Mode.

Performance issues on mid-range phones stem from oversized texture packs and thousand-entity spawn tests — start with lightweight GoreDoll swaps before full map replacements from our custom maps page. Thermal throttling feels like input lag on touch controls; reduce graphics settings in GoreBox options before blaming addon code.

When an addon works on PC but fails on Android, read the mod.io listing for platform tags. Authors must explicitly support mobile Lua APIs — porting guidance lives alongside PC workflows in our Workshop guide and official gorebox-modding.github.io documentation.