[ 1.20.1 ] Trying to disconnect the player from a Server and show a Disconnect message.

[CompetitiveShelter91]

I am trying to create a mod that has a blacklist of servers and when a server is blacklisted show the player the option to join anyways or go back to the server list.

Currently i got the disconnected screen to show up, but the client does not disconnect from the server and the back to server list button does not work.

This is my current code:

Minecraft.getInstance().setScreen(new DisconnectedScreen(Minecraft.getInstance().screen, Component.literal("WARNING"),Component.literal(Minecraft.getInstance().getCurrentServer().ip +" is blocked.")));

 

And this is the result:

 

i already tried to create a Screen but that did not work. It would be awesome if i could get the DisconnectScreen working.

 

[warjort]

Look how ConnectScreen.init() handles the cancel button.

Or what ClientLevel.disconnect() does if you are not in that screen.

Other than that, posting code snippets out of context in the forum won't get you much help.

Post an example build on github that reproduces your problem.

[CompetitiveShelter91]

I now found a way to show the disconnection screen, but the screen changes back after a short time to the pause screen. I think the client needs to disconnect from the Server. How do i achieve that?

I currently have all the code in my main class:
https://gist.github.com/obvTiger/ab54433cfb15f6cde0978288fd38833f

 

the commented code is just for testing purposes

Edited August 26, 2023 by CompetitiveShelter91

[warjort]

28 minutes ago, warjort said:

Look how ConnectScreen.init() handles the cancel button.

Or what ClientLevel.disconnect() does if you are not in that screen.

There is little point responding to your questions if you don't read the answers.

 

The code you posted looks wrong in many ways.

* It is still a code snippet instead of a build we can try ourselves to reproduce your probelm (not really relevant in this case)

* Using client classes in an event that can fired on the server

* Not checking the entity is the client player rather than some other entity (including remote players)

* The event is fired after the player joins the server/game - doesn't that defeat the point?