Repository navigation
Keep Forge's splash out of virtual-display checks - #518
Merged
SkyBlade1978 merged 1 commit intoOct 25, 2026
Merged
SkyBlade1978 merged 1 commit into
SkyBlade1978 merged 1 commit into
Conversation
SkyBlade1978
merged commit Oct 25, 2026
c07f6f3
into
MinecraftModDevelopmentMods:master-1.21.1
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.
The packaged client check got stuck in Forge's early splash window on two MMD runners. The game never reached the Base Metals checks.
This skips that splash only for the two virtual-display client smokes. Minecraft still opens its normal game window and runs the existing world, rendering and inventory checks. Ordinary launches are unchanged.
The offline build, unit tests, generated-data check, artifact audit and Eclipse isolation pass locally. The packaged client also passes with the new setting. All three release JARs are byte-identical to the previous local candidate.
There are no gameplay or save-migration changes in this follow-up.