Releases: architectury/architectury-loom
Releases · architectury/architectury-loom
Architectury Loom 1.13
Architectury Loom 1.11
- Requires Java 21, mods can still target Java 8 and any game versions
- Config cache support for more tasks
- quilt.mod.json5 support
- Major upstream changes: Unpick v3 support for newer Yarn builds, built-in RenderDoc support, custom mappings in
remap(Sources)Jartasks
See also: upstream changelog
Architectury Loom 1.7
- Stabilised NeoForge and Quilt support
- Stabilised
RunConfigSettings.mods - Bug fixes, see commit log
Architectury Loom 1.6
No downstream feature updates, only bug fixes. See Fabric's changelog for a list of upstream changes.
Architectury Loom 1.5
Changed
- Official Fabric TinyRemapper is now used instead of our custom fork. Support for MRJ jars (jars with classes that support different Java versions) should be better.
Upstream changes
- Full support for using Tiny Remapper to remap mixins
- Opt-in via
loom.mixin.useLegacyMixinAp = falsein build.gradle - Offers a small speedup compared to the mixin AP
- Opt-in via
- and more features and bug fixes at https://github.com/FabricMC/fabric-loom/releases/tag/1.5
Architectury Loom 1.4
Added
- NeoForge support
- Check for using MCPConfig/NeoForm (and Forge/NeoForge) data with the incorrect game version
- Can be disabled using the
loom.allowMismatchedPlatformVersionproject property
- Can be disabled using the
- Support for Minecraft Forge on MC 1.20.2+
Changed
- Improved log messages for experimental platforms
Fixed
- Missing field names when the type has been changed (#162)
Architectury Loom 1.3
Added
- A way to configure
ModSettingsper run config in Forge projects. This feature is useful for Forge mods with separate dev-only source sets (e.g. data generation). (#144 + #145)
Code example:loom { runs { data { // <data run config boilerplate> mods { // if non-empty, replaces the "global" mod settings container tinypotato { sourceSet sourceSets.main sourceSet sourceSets.data } } } } }
Fixed
Architectury Loom 1.2
- Added new
loom.forge.useForgeLoggerConfigproperty to use FML's logger config instead of Loom's. Usage:
loom {
forge {
useForgeLoggerConfig = true
}
}- Upstream changes:
- Updated to Gradle 8.1
- Better library handling, including automatic upgrade of LWJGL for Java 19+
- Updated Kotlin metadata remapping
- Run configs can now override the main class set by the mod loader
Architectury Loom 1.0
Architectury Loom 1.0
🎆 New features 🎆
genForgePatchedSourcesfor generating Minecraft sources using Forge's toolchain- Includes Forge's own comments in the code!
- Note: does not include any javadoc from mappings yet
- Loom's MCPConfig executor no longer executes unnecessary steps
🚫 Removed features 🚫
One focus of 1.0 was to simplify Loom's API and remove duplicate
features that were handled by multiple APIs.
ForgeLocalModandloom.forge.localModsin favour of usingloom.mods, which also works on FabricLaunchProviderSettingsandloom.launchesin favour of using run configs
🐞 Bug fixes 🐞
- Fixed Forge's own sources being replaced by decompiled ones
- Fixed decompiled game sources on Forge not having javadoc or parameters
@Overwritemixins from dependencies not working on Forge (also automatically included in other Loom versions)- Fixed Tiny v1 mappings crashing on Fabric
Also includes everything from Fabric Loom 1.0, go check out their changelog!