How to Install Bonelab Code Mods on Quest (Step-by-Step Guide)
Bonelab's modding community is one of the most active in VR gaming, and for good reason — the game was built with modification in mind. Installing code mods on the Meta Quest version, however, works differently from PC modding and trips up a lot of players. Here's a clear breakdown of what's actually involved.
What Are Code Mods in Bonelab?
Before diving into installation, it's worth separating two types of mods:
- Content mods — custom levels, avatars, and props. These are simpler to install and supported natively through Bonelab's in-game mod browser (powered by mod.io).
- Code mods — modifications that alter game logic, add new mechanics, or extend functionality through compiled code. These require a different approach entirely.
Code mods typically ship as .dll files and depend on MelonLoader, a mod loader framework. The challenge on Quest is that the headset runs Android, not Windows — so the pipeline looks quite different from the standard PC workflow.
What You Need Before You Start
Getting code mods running on a standalone Quest (Quest 2, Quest 3, or Quest Pro) requires a few prerequisites:
- Developer Mode enabled on your Quest headset
- SideQuest (the desktop app) or ADB (Android Debug Bridge) installed on your PC or Mac
- A USB-C cable for connecting your headset to your computer
- ThunderStore Mod Manager or manual mod files from a trusted source like thunderstore.io
- The Android-compatible build of any code mod you want to install — not all code mods have Quest ports 🎮
This last point is critical. Many popular code mods exist only for the PC (Steam) version of Bonelab. A mod compiled for Windows will not run on Quest's Android environment. Always verify the mod page specifically lists Quest / Android compatibility.
How the Installation Process Works
Step 1: Enable Developer Mode
On your phone, open the Meta app, navigate to your headset's settings, and toggle Developer Mode on. You'll need to join (or create) a Meta developer organization — it's free and takes about two minutes.
Step 2: Connect Your Quest to a PC
Use a USB-C cable to connect your headset to your computer. Put the headset on and accept the "Allow USB Debugging" prompt that appears inside the headset. Without this, your PC won't be able to interact with the device's file system.
Step 3: Install SideQuest (If Using the GUI Route)
SideQuest Advanced gives you a file manager and ADB interface in a more approachable package. Once connected, you can browse your Quest's storage directories directly.
Alternatively, if you're comfortable with command-line tools, raw ADB commands give you the same access with more precision.
Step 4: Locate the Correct Mod Directory
Bonelab stores its mod content in a specific folder path on the Quest's internal storage. The standard path is:
/sdcard/Android/data/com.StressLevelZero.BONELAB/files/Mods/ Code mods — specifically those compatible with the Quest build — go into a subfolder within this directory. The exact subfolder depends on whether the mod uses Bonelab's native mod loading system or a separate loader. Check the mod's README or installation notes for the precise target folder.
Step 5: Transfer the Mod Files
Using SideQuest's file manager or an ADB push command, transfer your mod files into the correct directory. A basic ADB push looks like:
adb push YourMod.dll /sdcard/Android/data/com.StressLevelZero.BONELAB/files/Mods/ Adjust the path and filename to match your specific mod.
Step 6: Launch Bonelab and Verify
Boot up Bonelab on your Quest. Code mods that are properly installed and Quest-compatible should load automatically. Some mods include an in-game indicator or menu entry confirming they're active; others simply modify behavior in the background.
Key Variables That Affect Your Results
Not every setup produces the same outcome. Several factors shape whether code mods work smoothly: 🔧
| Variable | Why It Matters |
|---|---|
| Quest model | Quest 2 vs Quest 3 have different hardware; some mods may perform differently |
| Bonelab version | Mods are often built against a specific game version; mismatches cause crashes |
| Mod architecture | Windows-only .dll files simply won't run on Android |
| Developer Mode status | Without it, file transfer is blocked entirely |
| Mod conflicts | Multiple code mods can interfere with each other |
Keeping Bonelab updated can also break previously working mods if the mod author hasn't pushed an update yet. Some players deliberately delay game updates to preserve a stable modded setup.
The Standalone Quest vs. PC Trade-Off
It's worth understanding why the Quest modding experience differs so fundamentally from PC. The PC version of Bonelab runs on Windows, where MelonLoader integrates deeply with the game executable. The Quest runs Android, which has a more restricted file system and a different runtime environment.
Not every mod that exists for PC will have a Quest version. The modding community does port popular code mods, but there's often a lag — and some mods never make the jump. Players who want access to the widest range of code mods typically keep a PC version alongside their Quest setup.
Your headset model, your comfort with ADB tools, the specific mods you want, and how often you're willing to maintain your setup when updates drop are all factors that determine how smooth — or complicated — this process ends up being for you specifically.