Repository navigation
Keep saved provider ore settings on Forge 26.2 - #340
Merged
Conversation
SkyBlade1978
merged commit Nov 12, 2026
a397353
into
MinecraftModDevelopmentMods:master-26.2
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.
Keep saved ore settings when a recognised provider rule is renamed. Add the
modern rule as a disabled, editable alternative without adding another ore pass.
This is the manually accepted Forge 26.2 repair, version 4.1.1.2602001.
It leaves existing chunks, saved formats and the public API unchanged.
Ambiguous matches and already-configured old/new pairs are preserved.
Validation:
Player SHA-256: BC0658DF2E149CC23E65E5771F3FF62E2BB13FFDA4E316AB632EB92EF7FA5A1F
This PR is only for Forge 26.2. Publication follows successful PR and merged-source checks.