Preserve legacy Mineralogy upgrades on Forge 1.17.1 - #224
Open
SkyBlade1978 wants to merge 3 commits into
Open
Conversation
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
1 participant
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.
Preserves upgrades for generated worlds made with Mineralogy 1.10, 1.12, or the exact 1.17.1 5.3.0 lineage. Saved mod metadata (including level.dat_old) selects the legacy Cyano contract; existing OreSpawn world profiles remain authoritative and fresh worlds are not changed merely because stale legacy files are installed.
Adds atomic, idempotent upgrade reports for legacy OreSpawn and Mineralogy imports while retaining original config files and existing chunks. The published Mineralogy 5.3.0 engine is used through an isolated test oracle and does not enter Gradle, Eclipse, or release artifacts.
Validation: 110 tests across 28 suites; 27 structured resources; 16 locales with 357 keys; full Java 16-target build, Javadocs and Eclipse lifecycle; fresh/reload surface gate with 101 stable real-water blocks; runtime log scanner clean; zero fixture/oracle leakage.
No version, public API, schema, registry ID, or provider meaning changes. Remaining gate: a quick player/UI test before merge.