Architectury Loom vs Neo-Loom

Architectury Loom is a free Gradle plugin for setting up development environments for Minecraft mods. It supports Fabric, Forge, NeoForge, and Quilt, and is described as a ForgeGradle replacement based on FabricMC Loom. Developers can choose Yarn, Official Mojang Mappings, or MCP mappings. Loom uses Fernflower and CFR to generate source code with comments. The documented IDE support is IntelliJ IDEA and Visual Studio Code; other IDEs are not tested or supported. The project requires Gradle 8.1 or newer and runs on Linux, macOS, and Windows. Its documentation labels the project experimental and says issues may arise, with reports directed to the issue tracker. The repository uses the MIT license, and community discussion is available through Discord. The latest listed release is 1.17, which includes an API for converting access wideners to access transformers for Forge and NeoForge.

Neo-Loom is a free Gradle plugin for Minecraft mod development environments using NeoForge or MinecraftForge. It is a fork of Fabric Loom and is heavily based on Architectury Loom. Implemented support includes NeoForge 1.21+ and MinecraftForge 1.20.1+. The plugin supports multi-loader projects, dependency management, client and server scope, and dedicated server support. It provides run configurations for NeoForge and MinecraftForge covering server data, client data, and game test server environments. Neo-Loom supports Jar-in-Jar packaging, converts ClassTweaker or AccessWidener files to AccessTransformer format, and supports publishing and consuming ModDevGradle-compatible Access Transformers and Interface Injections. Devlaunch is listed as implemented. Setup uses the Fabric and RelativityMC Maven repositories and the Gradle Plugin Portal, with plugin IDs shown in the README. The repository is MIT licensed and points users to Discord for support. Listed unfinished work includes JUnit, production launch tasks, and split-source, client-only, and server-only setups for (Neo)Forge.