Repository navigation
Update Modern Metals for Minecraft 1.11.2 - #132
Merged
SkyBlade1978 merged 1 commit intoNov 8, 2026
Merged
SkyBlade1978 merged 1 commit into
SkyBlade1978 merged 1 commit into
Conversation
Bring over the legacy build, settings and material fixes. Use the OreSpawn 4.1 provider and keep the existing 1.11.2 save IDs.
SkyBlade1978
merged commit Nov 8, 2026
aac9233
into
MinecraftModDevelopmentMods:master-1.11.2
3 of 6 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 brings the 1.10.2 updates over to 1.11.2. Modern Metals has its own Fantasy Level, and the settings open from both the Forge mod list and OreSpawn. The ores use the new overlays and OreSpawn 4 provider. Titanium still comes from rutile and magnesium by default, with an option to generate titanium ore.
The packaged server tests passed with the pinned local Base Metals and OreSpawn jars. I checked both config screens, upgrades from OS1 and OS3, and a copy of a world from beta4.58. Existing ore overrides survived the upgrade.
The wrapper check passed. The hosted build stopped at dependency download because the two pinned jars aren't on public Maven yet. Fork build
I'm holding the release until I've had time to do more manual testing.