modloaders

Discovers and installs Fabric, Quilt, Forge, and NeoForge versions into a shared Minecraft version cache.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/Sixdd6/grid-craft-launcher --skill modloaders-sixdd6
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: modloaders
Source: https://github.com/Sixdd6/grid-craft-launcher/tree/main/.claude/skills/modloaders
Command: npx skills add https://github.com/Sixdd6/grid-craft-launcher --skill modloaders-sixdd6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Installing Minecraft mod loaders requires querying four different metadata APIs, downloading installer jars, and running Forge/NeoForge processors headlessly, all with subtle per-loader quirks that are easy to get wrong. ## Core Features & Use Cases - Version Discovery: Lists available loader versions for Fabric, Quilt, Forge, and NeoForge through their respective metadata endpoints, including NeoForge's version-to-Minecraft mapping rules. - Headless Installation: Installs loader versions into cache/versions/ and cache/libraries/ with inheritsFrom version JSON, running Forge/NeoForge installer processors via a pluggable ProcessRunner test seam. - Cache Short-Circuiting: Skips all network and processor work when a repeated install finds a complete cache, using sha1 sidecar files to tolerate zlib-ng recompression differences. - Use Case: When adding NeoForge support to gcl-core, consult this Skill to learn that Minecraft 1.20.1 has no neoforge artifact and that 1.20.2 must be used for verification instead. ## Quick Start Read this Skill before modifying anything under gcl-core loaders/ so the loader install code follows the documented API endpoints and processor algorithm.

Frequently Asked Questions about modloaders

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

FAQPage Schema
How do I install Forge or NeoForge headlessly without the installer GUI?▼

Extract install_profile.json from the installer jar, download its libraries, then run each processor with java -cp using the manifest Main-Class and substituted data arguments. Never run the installer's own main class.

How do I list available NeoForge versions for a Minecraft version?▼

Query https://maven.neoforged.net/api/maven/versions/releases/net/neoforged/neoforge for the versions array. Up to major 25, version A.B.x maps to Minecraft 1.A.B; from major 26 the mapping follows Minecraft's year-based versioning.

Why does NeoForge have no build for Minecraft 1.20.1?▼

The 1.20.1 release line shipped as net.neoforged:forge 47.1.x under the old artifact name, so the neoforge artifact has no 1.20.1 build. Use Minecraft 1.20.2, the first version the neoforge artifact covers.

Why does Forge processor output hash verification fail on Fedora or Arch?▼

Mojang's java-runtime-gamma links libzip against the host zlib, which is zlib-ng on Fedora, Nobara, and Arch, producing different compressed bytes with identical content. Verify the jar by reading every entry's CRC32 instead of failing on the sha1 mismatch.

When is a repeated loader install a no-op?▼

A repeated install does no work only when the installer jar is still present in cache/installers/, because the profile listing processor outputs lives inside that jar. If the jar is missing, the full install runs again even if outputs are correct.