Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Neo-Loom review

Free#16 of 35 in Minecraft Mod Development Tools

An open-source Gradle tool for cross-toolchain NeoForge and MinecraftForge builds.

7.8/10Editor score
Neo-Loom7.8 Visit Neo-Loom

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Neo-Loom is an open-source Gradle build-system plugin for Minecraft mod development. It is designed for developers working across the NeoForge and MinecraftForge toolchains, with support documented for Minecraft 1.21+ and NeoForge 26.1+ configurations. Its scope centers on build configuration and development workflows rather than a general-purpose Minecraft editor, making it a fit for teams and individual developers already organizing mods with Gradle.

Its strongest feature is cross-toolchain coverage. Neo-Loom supports development launch configurations, Minecraft mapping configuration with Yarn and Modern Yarn, and Gradle-based mod artifact remapping. It also covers Jar-in-Jar packaging, ClassTweaker and AccessWidener to AccessTransformer conversion, and publishing or consuming access transformers and interface injections. Together, these capabilities address the build, mapping, launch, packaging, and compatibility tasks that arise when a project targets NeoForge or MinecraftForge.

The main trade-off is focus. The documented version range is centered on newer Minecraft and NeoForge releases, so projects built around older versions may not fit its current support direction. The Gradle-based workflow also makes it a specialized choice for developers who want build-system integration rather than a standalone development environment. Choose Neo-Loom when a project needs NeoForge and MinecraftForge support in one toolchain; consider a different option when the project targets other loaders, older versions, or a workflow outside Gradle.

Neo-Loom pros and cons

  • Where it wins
    • Supports both NeoForge and MinecraftForge toolchains
    • Handles mappings, access conversion, launches, and remapping
    • Includes Jar-in-Jar and artifact packaging workflows
  • Where it doesn't
    • Support is focused on newer Minecraft and NeoForge versions
    • Requires a Gradle-based development workflow
    • Best suited to NeoForge and Forge projects rather than broader loader needs

Neo-Loom fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update