Bring OreSpawn 4.1 to Forge 1.12.2 - #301
Merged
SkyBlade1978 merged 6 commits intoSep 29, 2026
Merged
SkyBlade1978 merged 6 commits into
SkyBlade1978 merged 6 commits into
Conversation
SkyBlade1978
merged commit Sep 29, 2026
a886942
into
MinecraftModDevelopmentMods:master-1.12.2
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
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.
This brings the 4.1 ore-source and biome-management work to Forge 1.12.2. It also tidies the build scripts and guides, and aligns the vendor and line-ending settings.
I ran the full offline build (276 tests), client integration, Eclipse checks, and a packaged Forge fresh/reload test. The local game config files were not included.