====== Using Mixins ======

As per traditional Loom fashion, Architectury Loom provides excellent Mixin support out of the box.
Architectury Loom also defaults into using the FabricMC's fork of Mixin for better refmap handling in development environments.

===== Dependencies with Mixin =====

Architectury Loom works with dependencies with mixin, Architectury Loom injects a remapper into your development environment to properly remap srg reference maps to named.
This is all handled for you in Architectury Loom, so you don't need to worry.

===== Do I need MixinGradle? =====

No.

For a matter of fact, MixinGradle is only responsible for adding the compiler arguments for the Mixin Annotation Processor to create the refmaps.
Architectury Loom uses its own [[https://github.com/FabricMC/fabric-mixin-compile-extensions | Mixin Compiler Extensions]] to create the refmaps, and support for it is directly added in Loom.

===== Declaring Mixins =====

Fabric Loader uses the ''fabric.mod.json'' to load mixin configs.

On Forge, the ''MixinConfigs'' argument is used instead. Loom will handle adding the arguments for you within both the development environment, and the compiled jar.

You must tell Loom what mixins you have by declaring the following in your ''build.gradle''.

<code groovy>
loom {
    forge {
        mixinConfig "mixin.examplemod.json"
    }
}
</code>