build-troubleshooting

Diagnose and resolve Gradle build and GameTest failures in Fabric/NeoForge Minecraft mods.

Updated Oct 19, 2025

Search Tags:#troubleshooting #build #gradle #CI #GameTest #NeoForge #Fabric

Ready to run

npx skills add https://github.com/ksoichiro/ChronoDawn --skill build-troubleshooting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-troubleshooting
Source: https://github.com/ksoichiro/ChronoDawn/tree/main/.claude/skills/build-troubleshooting
Command: npx skills add https://github.com/ksoichiro/ChronoDawn --skill build-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a centralized FAQ to diagnose and resolve common build and test failures in NeoForge/Fabric projects, helping developers quickly identify root causes and apply fixes.

Core Features & Use Cases

Step-by-step troubleshooting guidance for Gradle-based builds and GameTest failures (e.g., Illegal version number, session.lock) across Fabric and NeoForge environments.
Practical remediation workflows, including cleaning IDE artifacts, stopping and restarting Gradle daemons, and executing ./gradlew cleanAll.
Real-world scenarios with recommended, repeatable actions to reduce debugging time in local development and CI pipelines.

Quick Start

To start troubleshooting, follow these steps:

Stop Gradle daemons: ./gradlew --stop
Clean IDE artifacts and bin directories as applicable (e.g., rm -rf neoforge-/bin common-/bin)
Rebuild: ./gradlew cleanAll
Re-run tests: ./gradlew testAll or gameTestAll

Frequently Asked Questions about build-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix Gradle build failures in NeoForge and Fabric Minecraft mods?▼

Resolve GameTest failures by stopping Gradle daemons, cleaning IDE artifacts and bin directories, then rebuilding with ./gradlew cleanAll and re-running tests using ./gradlew testAll or gameTestAll.

Why does my Minecraft mod build fail with an Illegal version number or session.lock error?▼

Illegal version number or session.lock errors stem from version-lock conflicts and stale IDE artifacts; resolve them by removing bin directories and executing ./gradlew cleanAll to reset the build environment.

What is the best way to clean stale IDE artifacts for Fabric and NeoForge mod development?▼

Clean stale IDE artifacts by removing bin directories with commands like rm -rf neoforge-*/bin common-*/bin, then stopping Gradle daemons with ./gradlew --stop before executing a fresh build.

Does this troubleshooting workflow apply to both local development and CI pipelines for Minecraft mods?▼

Yes, the troubleshooting workflow applies to both local development and CI pipelines, providing structured remediation steps for Gradle daemon conflicts, missing bin directories, and build failures across Fabric and NeoForge environments.

How do I resolve Gradle daemon conflicts causing build failures in Minecraft mod projects?▼

Resolve Gradle daemon conflicts by running ./gradlew --stop to halt active daemons, clearing stale bin directories, and starting a fresh build process to eliminate state caching issues across Fabric and NeoForge environments.

When should I use ./gradlew cleanAll versus standard clean for Fabric and NeoForge builds?▼

Use ./gradlew cleanAll instead of standard clean when persistent build failures occur, as cleanAll clears cross-loader artifacts and stale bin directories across multiple Fabric and NeoForge subprojects simultaneously.