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.

Game logs are the fastest way to diagnose problems in QuestCraft. Every session generates a fresh log file that records exactly what happened — including any errors or crashes. QuestCraft provides two ways to access and share that log: a quick in-launcher method using the Discord bot, and a manual method using a file manager directly on your headset.

​
Easy Way — Using the Discord Bot

This is the recommended approach. The Crafty bot in the QuestCraft Discord can analyse your log automatically and flag known issues in seconds.
1

Join the QuestCraft Discord

Open discord.gg/questcraft and join the server if you have not already.
2

Go to #bot-commands

Navigate to the #bot-commands channel in the server. This is where you interact with the Crafty bot.
3

Get your log link from the launcher

In the QuestCraft launcher on your headset, press the Need Help? button. The launcher will upload your current log to mclo.gs and display the resulting link.
4

Download the log file

Open the mclo.gs link on your phone or computer and download the raw log file.
5

Upload to Crafty

Back in the #bot-commands channel, type /logs and attach the downloaded log file. Crafty will analyse it and respond with any errors it identifies.
This is the recommended method for getting support. The Discord community can quickly recognise common error patterns and point you straight to the fix — especially for mod conflicts and version mismatches.

​
Manual Way — Reading the Log Directly

If you prefer to inspect the log yourself, or if you cannot access Discord, you can open the file directly on your headset using any file manager app.
1

Open a file manager on your headset

Use a file manager app (such as the built-in Meta Files app, or a sideloaded manager like MiXplorer) to browse your headset’s storage.
2

Navigate to the QuestCraft data folder

Go to the following path:
Android/data/com.qcxr.qcxr
3

Open latestlog.txt

Locate and open the file named latestlog.txt. This file is overwritten at the start of every new session, so always check it immediately after a crash.
4

Scroll to the bottom of the file

The most important information is always at the end of the log. Scroll past the startup messages and version info to reach the most recent output.
5

Look for a Fabric error message

Search for an error block from net.fabricmc.loader — it will name the mod responsible for the crash. Here is an example of what it looks like:
[ERROR] net.fabricmc.loader: Could not load mod 'example-mod'
Caused by: java.lang.RuntimeException: ...
The mod name in single quotes is the one causing the problem.
You can skip step 3 of the manual process entirely by pressing the Need Help? button in the QuestCraft launcher — it will upload the log to mclo.gs and give you a shareable link immediately, without needing a file manager.
Once you have identified the problematic mod, head to the Mod Crashes guide for instructions on disabling it and restoring a working game state.

Build docs developers (and LLMs) love

Get started for freeTalk to us