Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
start [2022/09/12 10:54] – juuzstart [2023/08/27 16:05] (current) – grammer cosmicdan
Line 1: Line 1:
 ====== Welcome to the Architectury Wiki! ====== ====== Welcome to the Architectury Wiki! ======
  
-test contents below+Architectury is a toolchain aimed to ease developing multiplatform mods.
  
-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.+It consists of the optional [[api:introduction|Architectury API]], our [[loom:introduction|custom fork of Loom]], our [[plugin:introduction|custom Gradle plugin]] and [[https://plugins.jetbrains.com/plugin/16210-architectury|an Intellij IDEA plugin]] to go with all of it.
  
-==== 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.+For support and discussions, you may use the [[https://discord.architectury.dev|Architectury Discord Server]].
  
-==== Do I need MixinGradle? ==== +=== Get Started as a Dev === 
- +If you wish to build your mod for all the mod loaders out there, [[plugin:get_started|get started here]].
-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 ==== +
- +
-The Fabric Mod 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>+
  
 +If, instead, you want to manually replace ForgeGradle with Architectury Loom, read on [[loom:introduction|here]].