-
-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1.21.4] Revert Registries to Frozen on Disconnect when a connection is present #1934
Conversation
Last commit published: 2ea2e0c22efea2a89dbaddc0ad20661f8a05a4ae. PR PublishingThe artifacts published by this PR:
Repository DeclarationIn order to use the artifacts published by the PR, add the following repository to your buildscript: repositories {
maven {
name 'Maven for PR #1934' // https://github.com/neoforged/NeoForge/pull/1934
url 'https://prmaven.neoforged.net/NeoForge/pr1934'
content {
includeModule('net.neoforged', 'neoforge')
includeModule('net.neoforged', 'testframework')
}
}
} MDK installationIn order to setup a MDK using the latest PR version, run the following commands in a terminal. mkdir NeoForge-pr1934
cd NeoForge-pr1934
curl -L https://prmaven.neoforged.net/NeoForge/pr1934/net/neoforged/neoforge/21.4.82-beta-pr-1934-fix-i1932/mdk-pr1934.zip -o mdk.zip
jar xf mdk.zip
rm mdk.zip || del mdk.zip To test a production environment, you can download the installer from here. |
🚀 This PR has been released as NeoForge version |
This comment has been minimized.
This comment has been minimized.
Created backport PR: #1944 |
Closes #1932
Moves the call to
RegistryManager#revertToFrozen
toMinecraft#disconnect
to handle every case of the vanilla client disconnecting from some server instance. As we don't want to revert the registries until after all potential usecases are handled, the logic is cached before the connection is released and ran at the end of the method. There is no need to include the memory connection check as this is called regardless of the type of channel used, as evidenced by its prior use inServerLifecycleHooks#handleServerStopped
.The test provided in the issue was used to verify the logic.