Links
Tags
Creators
Details
All versions
0.3.6+neoforge.26.1.2
Release
0.3.6 (NeoForge, MC 26.1.2)3 weeks ago 13
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
Added
- NeoForge 26.1.2 and 26.2: provide dedicated server artifacts with the same native commands, loaded-chunk cleanup, statistics, item recovery, menus, reloads, temporary teleports, and update checks as Fabric.
- NeoForge permissions: integrate with the native PermissionAPI, register canonical nodes and compatibility aliases, and respect the selected handler's final boolean decisions.
- NeoForge item expiry: recover items through the native expiration event, respecting custom item lifespans and extensions from other mods. Real-server checks cover both early expiration and delayed recovery after a longer lifespan.
- Mod platform verification: use one real-server smoke suite for both loaders and both game versions, verify the packaged mod and matching Architectury API, and include all four mod artifacts in the manual Release workflow and separate Modrinth versions.
Changed
- Architectury modules: organize the project into
common,paper,mod-common,fabric, andneoforge. Both mod loaders share the native server implementation underorg.meowcat.eclean.mod; loader entrypoints remain in their own packages. - Development branch: use
architecturyas the default branch and the target of CI, release, and version-name maintenance workflows.
Upgrade notes
- Fabric and NeoForge now require the Architectury API JAR matching the server's game version. Fabric still requires Fabric API. Install these dependencies on the server; vanilla clients can continue to connect.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:VW7EmMIj:zmeqwSzm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VW7EmMIj:zmeqwSzm"
}

