minecraft-multiloader

To build a Minecraft mod for both Fabric and NeoForge, you use an Architectury-based multiloader structure with common, fabric, and neoforge subprojects. This setup isolates platform-specific behavior using ExpectPlatform implementations and loader entrypoints, keeping shared logic portable across loaders.

The Architectury layout for Minecraft 1.21.x organizes code into common, fabric, and neoforge subprojects. It uses ExpectPlatform implementations and loader entrypoints to isolate platform-specific differences while keeping shared logic portable across both Fabric and NeoForge.

Yes, Architectury handles platform-specific code using ExpectPlatform implementations and loader entrypoints. This keeps Fabric and NeoForge differences isolated within their respective subprojects while the common subproject maintains portable shared logic.

You fix cross-loader build errors and version mismatches in a multiloader mod by validating gradle.properties version pins, checking access widener and remap setup, and running the bundled sanity checker for loader compatibility. This ensures Fabric and NeoForge versions match the target Minecraft patch.

Yes, the multiloader setup validates Fabric and NeoForge versions against the target Minecraft patch. It checks gradle.properties version pins, access widener and remap setup, and runs a sanity-check script to ensure loader compatibility and release-safe output.

Version alignment issues when publishing dual jars occur when gradle.properties version pins are mismatched across Fabric and NeoForge subprojects. You resolve this by validating version pins and running the bundled sanity checker to ensure loader compatibility before release.