What problem does it solve?
Configuring Mixins for Architectury's multi-loader Minecraft projects is error-prone due to loader-specific differences. This skill provides a structured guide to unify and manage Mixin configurations across Fabric and NeoForge, reducing mismatch risks and build issues.
Core Features & Use Cases
- Loader-specific Mixin files: Fabric and NeoForge each require distinct configurations, including refmap handling and direct Mojang mappings.
- Common Mixin strategy: Reference common mixins for shared behavior while keeping loader-specific files separate.
- Build integration guidance: Helps ensure mixins are correctly wired into build.gradle and mod metadata.
Quick Start
To start, create or update a Mixin class in common/src/main/java/com/chronodawn/mixin/, then update the corresponding Fabric and NeoForge mixin JSON files as described in this guide. For example, add a new class and commit changes to both loader configs, ensuring the refMap is present for Fabric and omitted for NeoForge.