Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/QuestCraftPlusPlus/QuestCraft/llms.txt

Use this file to discover all available pages before exploring further.

Mod crashes are the most common issue players encounter in QuestCraft. The good news is that most crashes leave a clear fingerprint in the game log — a Fabric error at the bottom of the file that names the responsible mod directly. Once you know which mod is at fault, fixing it is straightforward.

​
Identifying the Crash

Before you can fix a mod crash, you need to know which mod caused it. The log file is your primary tool.
  • Open latestlog.txt located at Android/data/com.qcxr.qcxr using a file manager on your headset.
  • Scroll to the bottom of the file and look for an error block from net.fabricmc.loader — it will name the offending mod.
  • Alternatively, press the Need Help? button in the QuestCraft launcher to instantly upload your log to mclo.gs and get a shareable link — no file manager needed.
For full instructions on finding and reading the log file, see the Reading Logs guide.

​
Fixing the Crash

Once you know (or suspect) which mod is responsible, follow these steps to disable it and get the game loading again.
1

Open the QuestCraft launcher

Launch the QuestCraft app from the Unknown Sources section of your headset’s app library.
2

Navigate to mod management for your instance

Select the Minecraft version instance you were using when the crash occurred, then open its Mod Manager or settings panel.
3

Disable the identified mod

Find the mod named in the log error and toggle it off. All preinstalled mods (except Vivecraft and Fabric API) can be toggled on and off per instance.
4

If unsure, disable recently added mods one at a time

If the log did not clearly name a mod — or you added several mods at once — disable the most recently added one first, then relaunch to test. Repeat with each mod in reverse order of installation until the crash stops.
5

Relaunch the game

Press Play and wait for the game to load. Monitor the log viewer in the launcher for any new errors.
6

Confirm the fix

If the game loads successfully, the mod you disabled was the cause of the crash. You can now decide whether to leave it disabled, look for a compatible version of that mod, or remove it entirely.
Vivecraft and Fabric API cannot be disabled — they are core components that QuestCraft depends on. If the error in your log points to either of these, the root cause is likely a third-party mod that is incompatible with them rather than a problem with Vivecraft or Fabric API themselves.

​
Mod Compatibility Rules

Not every Fabric mod works with QuestCraft. Before installing any mod, check it against these requirements:
Before installing a mod, make sure it meets all of the following:
  • Minecraft version match — The mod must be built for the exact Minecraft version your instance is running (e.g., a 1.20.1 mod will not work on a 1.21.1 instance).
  • Fabric only — QuestCraft uses the Fabric mod loader. Forge mods are not compatible and will crash the game on load.
  • VR compatibility — Mods that heavily modify rendering pipelines, input handling, or the HUD may conflict with Vivecraft. If a mod works in desktop Fabric but crashes in QuestCraft, this is a likely cause.

​
Getting Help

If you have worked through the steps above and still cannot identify or fix the crash, bring your log to the QuestCraft community:
  • Post in the #support channel of the QuestCraft Discord
  • Include your mclo.gs link (generated via the Need Help? button in the launcher) so the team can see the full log
If you determine that the crash is caused by a bug in QuestCraft itself — and is not related to any mod — please file an issue at github.com/QuestCraftPlusPlus/QuestCraft/issues. Before submitting, search the existing issues to make sure it has not already been reported. Duplicate reports slow down the team’s ability to triage and fix real bugs.

Build docs developers (and LLMs) love

Get started for freeTalk to us