Skip to content
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

Fix CarpetClient not disconnecting when leaving multiplayer #1913

Closed

Conversation

altrisi
Copy link
Collaborator

@altrisi altrisi commented May 5, 2024

Fixes #1908.

The issue was that the new transfer packets changed the signature of the disconnect method, but left a shortcut with the old one, that is no longer called when disconnecting. This should also make Carpet work properly when the client is being transferred between Carpet/non-Carpet servers (or just with different rules).

This removes the ClientCommonPacketListenerImpl mixin given it seems to not do anything anymore, and it was added with the network refactor.

Doesn't seem to be called, and the MinecraftClient one should be enough
@sakura-ryoko
Copy link

People are always asking me about this crash; FYI .

Heitzenberg added a commit to Heitzenberg/fabric-carpet that referenced this pull request Aug 13, 2024
Resolved conflicts with ClientCommonPacketListenerImpl_customPacketMixin.java
- Deleted the file as it was removed in the pull request
- Merged changes from MinecraftMixin.java and carpet.mixins.json
@magicus
Copy link

magicus commented Sep 23, 2024

@gnembon Any chance this could be integrated? It's highly annoying to have carpet crash Minecraft each time you switch to a local world. :-(

@gnembon gnembon closed this Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Client crash when leaving singleplayer world after having been in Carpet server
4 participants