mixin-guide

Automate Mixin configuration for Architectury multi-loader Minecraft projects.

Updated Oct 19, 2025
One-click install
npx skills add https://github.com/ksoichiro/ChronoDawn --skill mixin-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mixin-guide
Source: https://github.com/ksoichiro/ChronoDawn/tree/main/.claude/skills/mixin-guide
Command: npx skills add https://github.com/ksoichiro/ChronoDawn --skill mixin-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about mixin-guide

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

FAQPage Schema
How do I configure Mixins for Architectury multi-loader Minecraft projects?

Configuring Architectury Mixins requires maintaining distinct Fabric and NeoForge JSON files, keeping common mixins for shared behavior, and ensuring the refmap is present for Fabric but omitted for NeoForge.

Why does my Mixin setup break when switching between Fabric and NeoForge loaders?

Mixin setup breaks across loaders due to mismatched configurations, specifically incorrect refmap handling for Fabric versus direct Mojang mappings for NeoForge, causing build issues and runtime crashes.

Do I need separate mixin JSON files for Fabric and NeoForge in Architectury?

Yes, Architectury requires separate mixin JSON files for Fabric and NeoForge to handle loader-specific differences, while referencing common mixins for shared behavior to avoid mismatch risks.

How do I add a new Mixin class to an Architectury project?

To add a Mixin class, create it in the common source set, then update both Fabric and NeoForge mixin JSON files, ensuring the refmap is configured correctly for the Fabric build.

What is the correct refmap usage for Mixins in NeoForge and Fabric?

Correct refmap usage dictates that the refmap must be included in Fabric mixin configurations to remap intermediary names, while NeoForge uses direct Mojang mappings and omits the refmap entirely.

How do I integrate Architectury Mixin configurations into build.gradle?

Build integration requires wiring mixin configurations into build.gradle and mod metadata, ensuring both Fabric and NeoForge resources correctly process common and loader-specific mixins during compilation.