Tags
Creators
Details
All versions
1.1.0-forge-26.2
Release
Nerospace 1.1.0 - Forge 26.23 days ago 4
Compatibility
Minecraft: Java Edition
26.2
Platform
Forge
Supported environments
Client and server
Changes
Minecraft 26.3 support, plus one advancement fix.
Added
- Minecraft 26.3 as a new Stonecutter node on every loader — NeoForge
26.3.0.7-beta, Forge26.3-66.0.2and Fabric (fabric-api0.161.0+26.3, NeoForm26.3-1) — built alongside 26.1.2 and 26.2, so every release now ships nine loader × version jars.
Changed
- VS Code run/debug configurations (
.vscode/launch.json,.vscode/tasks.json) gain the three 26.3 cells; the "Build all" task now builds all nine. - CI (
multiloader.yml,publish.yml) builds, attaches and publishes the 26.3 jars. - Requires Neroland Core 1.13.0 (was
1.10.0) — the first Core release with a 26.3 build. The loader range still derives from the pin ([${nerolandcore_version},2.0)). - JEI pins moved to the newest published builds on each Minecraft version:
29.40.0.101(26.1.2),30.35.0.223(26.2) and31.3.0.18(26.3). Compile-time API only — JEI remains a soft dependency and the shipped jar gains no hard requirement. Thecompat/jeiplugin compiles unchanged against all three. - Now ships the
nerolandcore:battery,nerolandcore:fluid_tank,nerolandcore:gas_tankandnerolandcore:item_storerecipes (moved here from Neroland Core, ids unchanged). They are keyed onc:ingots/nerosiumandc:ingots/nerosteel, which Nerospace owns — keeping them in Core made a Core-without-Nerospace world fail to load on 26.3, where recipes are a datapack registry and a missing ingredient tag is fatal.
26.3 port notes
- Block classes build their codecs through Core's
BlockCodecs(26.3 removed block-type codecs);codec()is kept without@Overrideso one source compiles on every version. - 26.3 API differences are handled with Stonecutter blocks:
PoseStack#rotate(wasmulPose), the newPredictionargument ondrop/placeItemBackInInventory,setPermanentlyInvulnerable, and similar renames. - Worldgen: Hamlet, Ruin and Mega-City implement 26.3's data-driven
Featureinterface; their codecs are registered inFEATURE_TYPE, and the ore and structure features ship asworldgen/feature/*.jsonin theresources-26.3overlay. Theconfigured_featureJSON stays in place for 26.1.2 / 26.2. - Falling meteors and rockets use
LinearInterpolationHandleron 26.3, whereEntityowns interpolation. - Fixed: the New Life guide advancement never loaded, because its entity predicate used the legacy
typekey. It now usesminecraft:entity_type, with a 26.3 variant in the overlay. - Build: the shared
common/Java source is now preprocessed by Stonecutter for every non-active node (stonecutterProcessCommon), so common code can carry//? if >=26.3 {blocks, andcommon/src/main/resources-<mc>overlay folders are merged over the shared resources for matching nodes (mergeCommonResources). The active node still compiles the rawcommon/folder. - Build plugins aligned with Neroland Core: ModDevGradle
2.0.147(the older 2.0.141 cannot set up NeoForge 26.3), ForgeGradle7.0.40, Stonecutter0.9.8.
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:MZjgyY44:xVjd6kDx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MZjgyY44:xVjd6kDx"
}

