Port OreSpawn 4.0.16 to Forge 1.16.5 - #291
Merged
SkyBlade1978 merged 9 commits intoSep 7, 2026
Merged
Conversation
Contributor
Author
|
CI follow-up is fixed in The failure was confined to hosted build setup: ForgeGradle 7 requested a Java 25 toolchain for Minecraft Mavenizer during configuration, while the 1.16 workflows installed and exposed only Java 8 and Java 17. The repair installs pinned Temurin 25 first, retains Temurin 8 for compilation/fixtures, installs Temurin 17 last so it remains Verification:
This is build/CI documentation only: OreSpawn runtime code and version |
SkyBlade1978
merged commit Sep 7, 2026
203794d
into
MinecraftModDevelopmentMods:master-1.16.5
5 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Ports the accepted OreSpawn 4.0.10–4.0.16 campaign to Forge 1.16.5 and
finishes at
4.0.16.116051.This retains the existing 4.0.8 field-persistence work and the 4.0.9 natural
terrain-host repair, then adds:
formation identity;
BiomeDictionary, with stableRegistryKey<Biome>ore filters;contracts using the existing provider JSON fields;
top + 1, while preserving buried orauthored Snow/Ice and unsafe source states;
sampling, using
BiomeContainer.getNoiseBiomeandBiomeManager.getNoiseBiomeAtQuartwith correct negative-coordinate floorsemantics.
Forge 1.16 has no server-side GameTest harness class, so the 4.0.16
GameTest-ownership repair is recorded as target-inapplicable. The existing
ordinary dedicated-server benchmark auto-stop remains in place and is covered
by a real packaged benchmark.
Target-specific build and compatibility work
Java 8 bytecode, pack format 6, API 1 and schemas 4/6/5.
bin/mainMOD_CLASSESentries and production-only Eclipse launches.
and Java 17 Gradle execution. Empty-cache qualification confirmed that Forge
36 needs no Mavenizer compatibility patch.
documentation to
4.0.16.116051.No API major, schema, registry ID, provider-field meaning, profile filename,
migration behavior or existing chunk is changed. Compatibility remains
[4.0.6,5.0.0).Validation
a6bc7ee3f621b71b46025ee91b976d4d51e9b07a.in both the primary checkout and a cold exact-commit worktree.
including world creation, rendering, editors, save/reopen and clean stop.
flowing-fluid and sampler-attribution regressions pass fresh and reload.
ms/chunk. Sky is +7.849% direct and -5.339% control-normalized versus the
accepted 4.0.9 evidence, below the 10% investigation threshold.
B3D61A15F44845A5AB3A3869338BBA7E867F24F32275A03FAE28BC3B4029DE22.This PR updates MMD source only. It does not create a tag, publish artifacts,
update issues or directly modify the MMD target branch.