Quest Doctor

🩺 Quest Doctor

Quest Doctor audits existing FTB Quests books for pack authors before release.

Run one command and get a precise, read-only report for broken references, duplicate IDs, missing registry entries, suspicious progression, and raw quest definitions that do not match what FTB Quests actually loaded.

🔎 What it checks

• Duplicate FTB quest object IDs
• Missing chapter-group references
• Dangling quest/chapter dependencies
• Missing recognized quest-link targets
• Missing task or reward types
• Missing item, block, entity, and fluid registry entries
• Unresolved quest icons
• Chapter filename mismatches
• Empty reward tables
• Suspicious unreachable progression chains
• Raw quest counts vs. the loaded FTB Quests runtime model

📋 One-command audit

Use:

/questaudit

or:

/questdoctor audit

Quest Doctor prints a short result in chat and writes the detailed report to:

logs/questdoctor/quest-audit-<timestamp>.txt

Every finding includes an issue code and source location so you can go directly to the affected chapter or quest definition.

🛡️ Read-only by design

Quest Doctor never automatically rewrites your FTB Quests files.

It diagnoses problems. You decide what should change.

That makes it safe to use as a modpack release check without handing an automated fixer control over your progression design.

⚙️ Requirements

Minecraft 1.20.1 • Forge 47.4.10+ • Java 17 • FTB Quests 2001.4.x

Designed as a server-side pack-author/admin utility. For singleplayer pack development, install it normally in the development instance so the integrated server can run the audit.

💡 Recommended workflow

Edit quests → reload/restart → run Quest Doctor → fix real findings → playtest → release.

Quest Doctor catches structural/data problems before you spend time manually walking the entire quest progression.