-
-
Notifications
You must be signed in to change notification settings - Fork 134
Cant see Chat or Players #145
Comments
Can you post a proxy log? |
So.. Now everytime a Bedrock client joins and logs in the Client crashes. Console screenshot: https://gyazo.com/5f803628bf3b3fc669b16a0b6913f8d2 |
Ok, what version of Java are you using? |
"Java Version 9.0.1 (build 9.0.1+11) amd 64" |
Java 9 is NOT supported, please switch to Java 8. ;) |
We need to write it in the readme |
Changing to Java 8 has fixed the login issues, but Bedrock Client still is unable to see server chat or players. [Edit] |
Is it a 1.8 like server? With a protocole conversion 1.8 to 1.12.2? It can be the problem. |
Its 1.12.2 server, it has all the blocks and items. |
Ok, i don't know where does it come from. We have to investigate. |
Ill ask if I can get the BungeeCord version as well as the Spigot server version the server is using if that will help any. |
Ok, thanks. |
So I did a test with a random server and Chat and players do work to some extent. [Edit] |
@TheMasterBlaster pls try to use the latest dev one, i fixed a critical bug of chunk translation which crashes the clients. |
Iv not had any issue with Client crashes since I changed the Java Version the other day. |
@TheMasterBlaster but pls still build using latest |
I think that is what Im doing but I am not 100% sure. |
client will not be updated if you got disconnected from remote server so maybe you were kicked. |
Have you tried with the latest release? |
sometimes it just like being disconnected, no updates, no shit. maybe I suppressed some Exceptions by catching them?? |
Ok, so we have to handle server disconnect properly, im also having an issue with that on localhost, if you shutdown the minecraft server, the proxy don't handle the disconnection. |
yeah xD |
When using the 0.3.0 version of DragonProxy on a 1.12.2 server the Bedrock player is not getting Chat or Player movement updates. But Java players can.
[Edit] Java server was "mc.gingycraft.net", and also uses Bungeecord.
The text was updated successfully, but these errors were encountered: