Bug: reconnecting after stop command fixed
This commit is contained in:
@ -43,6 +43,5 @@ Do not repeatedly stop and start the queue, eventually you will not be able to l
|
||||
|
||||
# Known issues
|
||||
- starting the queue will revoke your minecraft token. this means that you will not be able to join normal minecraft servers until you restart the game
|
||||
- Some people report not being able to ride animals using this proxy.
|
||||
- 2b2t sometimes bugs out and removes you from the queue without telling you. In this case, your queue position will no longer move. Reconnect to fix this.
|
||||
- If you connect after the the queue is finnished or reconnect the proxy will send cached chunk data. Otherwise you would fly in a emtpy world. Other data however like entities are not chached and will not displayed correctly. You can move out of render distance and come back to fix this issue. Sometimes the client renders a cached chunk with a blank texture.
|
||||
|
||||
Reference in New Issue
Block a user