Repository navigation
Finish the 6.1.4 stone compatibility fixes for Forge 26.3 - #178
Merged
SkyBlade1978 merged 6 commits intoOct 7, 2026
Merged
SkyBlade1978 merged 6 commits into
SkyBlade1978 merged 6 commits into
Conversation
SkyBlade1978
merged commit Oct 7, 2026
8ac335f
into
MinecraftModDevelopmentMods:master-26.3
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.
This finishes the stone compatibility fixes for Mineralogy 6.1.4 on Forge 26.3.
Existing worlds get the behaviour fixes after updating. Cave decoration changes apply to new chunks; this won't redecorate explored caves. Vanilla and other mods' tag entries are preserved, with cobblestone equivalence both on and off.
This is
6.1.4.2603001for Minecraft 26.3, Forge 66.0.0 and Java 25, using released OreSpawn4.0.16.2603001. Registry IDs, configs, migrations, textures, enabled recipes and OreSpawn's provider/settings are unchanged.Local checks pass: 79 tests, release and Eclipse gates, two matching assemblies, both cobblestone modes and disabled construction, real behaviour tests, paired 81-chunk cave samples, and packaged client/server fresh starts and reloads. Complete logs were reviewed; platform and offline-account messages are accounted for, with no crashes or unexplained product failures. Agent notes and generated test output aren't committed, and probes don't ship.
The wider OreSpawn generation and legacy-world qualification is inherited from the unchanged port rather than rerun for these fixes. This replaces the earlier partial candidate and its broader sulfur-cube policy.