https://docs.architectury.dev/ 2026-04-10T01:26:39+00:00 https://docs.architectury.dev/ https://docs.architectury.dev/_media/wiki/logo.png text/html 2025-11-07T13:56:45+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/access_transformer?rev=1762523805&do=diff Access Transformer Access Transformers must be created in META-INF/accesstransformer.cfg, in the usual mappings of the mod loader: * Forge 1.16.x and earlier: MCP class names and SRG * Forge 1.17.x and later: Mojang class names and SRG * NeoForge: Mojang mappings text/html 2025-11-07T13:56:45+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/architectury_common_json?rev=1762523805&do=diff architectury.common.json architectury.common.json is a mod metadata format for common modules of cross-platform mods. These files can be placed at the top level of mod sources to provide some features -- interface injection and access wideners -- in development environments. text/html 2025-11-07T13:56:45+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/datagen?rev=1762523805&do=diff Forge Data Generators NOTE: This is only for Forge projects! Data Generators are still in development for Architectury projects. Fabric projects can follow Fabric Loom documentation. To make Data Generators work, we first need to add the src/generated folder to the resources classpath. text/html 2025-11-07T13:56:45+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/debug_log_level?rev=1762523805&do=diff Changing Log Level Property fabric.log.level (Defaulted info) is used for managing the log level to SOUT. You can override this property by declaring the following: loom { launches { client { property "fabric.log.level", "debug" } server { property "fabric.log.level", "debug" } } } text/html 2025-11-07T13:56:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/fg_mixin_refmaps?rev=1762523806&do=diff Fixing ForgeGradle Mixin refmaps TL;DR: Follow the following GitHub comment. The following applies to FG3 and sub-sequence versions if there are no fixes regarding this issue. Addressing some misconceptions Setting the property mixin.env.disableRefMap is not a proper fix, it may work for projects *with the same mappings*, as you are expecting that the original source of the mixin files to be in the same mappings as your development environment, which is false for some projects. (And is extr… text/html 2025-11-07T13:56:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/introduction?rev=1762523806&do=diff Architectury Loom Architectury Loom is a replacement plugin to ForgeGradle, based on FabricMC Loom. ---------- Things to know Limited IDE Support Architectury Loom currently only supports IntelliJ IDEA and Visual Studio Code. Other IDEs are not tested and are not supported. Unstable + Issues text/html 2025-11-07T13:56:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/mixins?rev=1762523806&do=diff 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 text/html 2025-11-07T13:56:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/regen_run_configs?rev=1762523806&do=diff Regenerating Run Configurations IntelliJ IDEA Delete the run configurations and refresh Gradle. (You can do this by the run configs prompt) If the run configurations do not show up after refreshing Gradle, try closing the IDEA project and reopening it, or choosing the text/html 2025-11-07T13:56:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/sidebar?rev=1762523806&do=diff Architectury Loom * Introduction * Using NeoForge * Using Libraries * Access Transformers * Using Mixins * Using Legacy MCP (1.16.5 or lower) * Fixing ForgeGradle Mixin refmaps * Forge Data Generators * Regenerating Run Configurations * Changing Log Level * Gradle Configurations * architectury.common.json text/html 2025-11-07T13:56:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/using_libraries?rev=1762523806&do=diff Using libraries External libraries can be used in mods built using Architectury Loom very much like in normal Gradle projects by adding them as Gradle dependencies. The exact setup, however, depends on the kind of library and the targetted mod loader. text/html 2025-11-07T13:56:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/using_mcp?rev=1762523806&do=diff Note: MCP is no longer used since Minecraft 1.17, and has been replaced with Official Mojang Mappings. Experimental MCP support is available in Architectury Loom. MCP docs and parameter mappings are fully supported in Forge Loom. However, MCP will not text/html 2025-11-07T13:56:46+00:00 Anonymous (anonymous@undisclosed.example.com) https://docs.architectury.dev/loom/using_neo?rev=1762523806&do=diff Using NeoForge NeoForge support has been added into Architectury Loom 1.2+. See the NeoForge migration guide for using NeoForge with Minecraft 1.20.2+. Instructions (Minecraft 1.20.1) 1. Replace the forge code in the build.gradle dependencies block: forge "net.neoforged:forge:VERSION"