CurseForge Gradle Publish Plugin vs Neo-Loom

CurseForge Gradle Publish Plugin publishes build artifacts to CurseForge from a Gradle build. A publication can specify a CurseForge project ID, main artifact, game versions, display name, release type, changelog, and artifact relationships. It uses the CurseForge Upload API and needs an API token in the plugin’s curseforge extension. The README warns that keeping the token in a version-controlled build script can expose it; user-specific Gradle properties are suggested instead.

For mod projects, the plugin can derive publication details from other tools. With Fabric Loom and a remapJar or jar bundling task, it can create a publication preconfigured for Fabric and the targeted Minecraft version. Its ModDevGradle and NeoGradle integrations can infer NeoForge and Minecraft-version details. When Gradle’s java-base plugin is present, it infers the Java version from the compileJava target.

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.