What problem does it solve? Building correct Minecraft launch commands requires interpreting Mojang's version manifest, version JSON, library rules, natives, argument placeholders, and Java runtime metadata, and mistakes in any of these produce broken installs or failed launches. ## Core Features & Use Cases - Manifest and version JSON handling: Cache the version manifest with ETag, resolve version JSONs by sha1 URL, and handle fields like downloads, libraries, arguments, mainClass, assetIndex, javaVersion, inheritsFrom, and logging. - Rules and natives resolution: Evaluate allow/disallow rules by OS name, arch, version, and feature flags; extract legacy natives classifiers into cache directories and pass -Djava.library.path. - Loader profile merging: Resolve inheritsFrom for Forge, NeoForge, and Fabric profiles with child-wins mainClass, appended arguments, per-key library merging, and special logging merge behavior. - Java runtime and GC probing: Download Mojang java-runtime components per platform and probe JVM garbage collector support via -XX:+PrintFlagsFinal with a cached, mtime-keyed result. - Use Case: When modifying launch argument code in gcl-core, consult this Skill to correctly expand placeholders like ${auth_player_name} and ${classpath} and merge a Forge profile over vanilla without losing Mojang's sha1 checksums. ## Quick Start Read this Skill before writing or changing anything in gcl-core mojang/ or java/ directories or any launch argument code.