Skip to content

Releases: architectury/architectury-loom

Architectury Loom 1.7

07 Dec 14:28
f9cfe89
Compare
Choose a tag to compare
  • Stabilised NeoForge and Quilt support
  • Stabilised RunConfigSettings.mods
  • Bug fixes, see commit log

Architectury Loom 1.6

02 Jul 16:36
49ef4fc
Compare
Choose a tag to compare

No downstream feature updates, only bug fixes. See Fabric's changelog for a list of upstream changes.

Architectury Loom 1.5

04 Apr 14:28
Compare
Choose a tag to compare

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

Architectury Loom 1.4

24 Jan 13:51
acd9ad7
Compare
Choose a tag to compare

Added

  • NeoForge support
  • Check for using MCPConfig/NeoForm (and Forge/NeoForge) data with the incorrect game version
    • Can be disabled using the loom.allowMismatchedPlatformVersion project property
  • 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

24 Sep 19:16
Compare
Choose a tag to compare

Added

  • A way to configure ModSettings per 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

  • Order of jars in fabric.mod.json depending on HashSet iteration order (#155)
  • JIJ not working for Forge libraries without a mods.toml (#152)

Architectury Loom 1.2

21 Jun 18:35
e0efe9c
Compare
Choose a tag to compare
  • Added new loom.forge.useForgeLoggerConfig property 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

30 Oct 14:52
Compare
Choose a tag to compare

Architectury Loom 1.0

🎆 New features 🎆

  • genForgePatchedSources for 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.

  • ForgeLocalMod and loom.forge.localMods in favour of using loom.mods, which also works on Fabric
  • LaunchProviderSettings and loom.launches in 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
  • @Overwrite mixins 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!