Prerequisites
Minecraft Version
1.20.4
Console Client Version
459
Expected Behavior
Reconnecting AutoRelog
Actual Behavior
After displaying "connection lost," it says it will reconnect after a while, but it doesn't. In fact, the MCC freezes and nothing can be typed.
This also happens when you left-click on CMD a few times, scroll down (to see the messages above), wait for a minute (this time may vary), and then click any key on the keyboard.
I can log in to the server when I close and reopen cmd.
The connection was interrupted because my internet connection went down momentarily, or my connection to the server was lost for a short time. AutoRelog shouldn't stop in this situation; it should keep trying to reconnect.
This happened when switching from a 2.4GHz to a 5GHz Wi-Fi connection (and vice versa).
This error doesn't occur in version 456, but it does in versions 459, 458, and 457. (I tested it.)
Steps to Reproduce the bug
- internet outage
- disconnect and reconnect the internet connection
Attach screenshot here (If applicable)
No response
Anythings that could help diagnosing the bug
Device
Desktop
Operating System
Windows
Server Address (If applicable)
No response
Prerequisites
debugmessages=truein config to diagnose my issueMinecraft Version
1.20.4
Console Client Version
459
Expected Behavior
Reconnecting AutoRelog
Actual Behavior
After displaying "connection lost," it says it will reconnect after a while, but it doesn't. In fact, the MCC freezes and nothing can be typed.
This also happens when you left-click on CMD a few times, scroll down (to see the messages above), wait for a minute (this time may vary), and then click any key on the keyboard.
I can log in to the server when I close and reopen cmd.
The connection was interrupted because my internet connection went down momentarily, or my connection to the server was lost for a short time. AutoRelog shouldn't stop in this situation; it should keep trying to reconnect.
This happened when switching from a 2.4GHz to a 5GHz Wi-Fi connection (and vice versa).
This error doesn't occur in version 456, but it does in versions 459, 458, and 457. (I tested it.)
Steps to Reproduce the bug
Attach screenshot here (If applicable)
No response
Anythings that could help diagnosing the bug
Device
Desktop
Operating System
Windows
Server Address (If applicable)
No response