Universal ViaVersion 1.6.0

Allow newer versions to connect, why lose players while waiting after a Minecraft update?

  1. Clicking on signs such as serversigns or skript signs do not work for 1.9s.
     
  2. FormallyMyles

    Supporter

    Console errors? this screen shot is useless.
     
  3. I get no console errors
     
  4. I have never seen this issue in my console since the recent installation of ViaVersion. Might want to look into this, i believe ViaVersion is at fault. Heres a screenshot of what console is spamming: http://prntscr.com/abo2kg
     
  5. FormallyMyles

    Supporter

    Use version 0.5.2, we accidentally released a debug version :)
     
  6. FormallyMyles

    Supporter

    Don't use reloads :) reboot
     
  7. @Mylescomputer how does the bungeecord version works? Just need to put on bungee plugins folder or need to put on on all spigot servers as well?
     
  8. minoneer

    Benefactor

    Hey,

    first of all: great plugin to close the gap between Minecraft 1.9 release and a stable 1.9 server configuration - thanks for the work!

    I have come across three bugs after loading the plugin version 0.5.2 on spigot 1.8.8:

    1. When accessing brewing stands, the player inventory is desynchronized. Items get mixed up, some stacks duplicate, others are set to wrong locations. Those items are client side only, reconnecting (or otherwise resynchronizing the inventory) fixes the issues. I assume it is because of the new slot in brewing stands.

    2. Not sure what exaclty is causing this, but there seems to be a problem with Minecarts as well, see server logs: http://pastebin.com/1hAzpGCL

    3. Another somewhat random bug which I could not directly relate to this plugin, but it starte occuring after adding it (never seen before): http://pastebin.com/aceMtwCZ

    Regards, minoneer
     
  9. FormallyMyles

    Supporter

  10. 1.9 clients can't join server if server is having score board
     
    • Like Like x 1
  11. 05.03 19:15:15 [Server] INFO at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    05.03 19:15:15 [Server] INFO at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    05.03 19:15:15 [Server] INFO at org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:56)
    05.03 19:15:15 [Server] WARN org.apache.commons.lang.UnhandledException: Plugin ViaVersion v0.5.3 generated an exception while executing task 380
    05.03 19:15:15 [Server] WARN Exception in thread "Craft Scheduler Thread - 2"
    05.03 19:15:15 [Server] WARN at java.lang.Thread.run(Thread.java:745)
    05.03 19:15:15 [Server] WARN at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    05.03 19:15:15 [Server] WARN at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    05.03 19:15:15 [Server] WARN at org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftAsyncTask.run(CraftAsyncTask.java:53)
    05.03 19:15:15 [Server] WARN at org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftTask.run(CraftTask.java:71)
    05.03 19:15:15 [Server] WARN at us.myles.ViaVersion.update.UpdateUtil$1.run(UpdateUtil.java:32)
    05.03 19:15:15 [Server] WARN at us.myles.ViaVersion.update.UpdateUtil.access$000(UpdateUtil.java:20)
    05.03 19:15:15 [Server] WARN at us.myles.ViaVersion.update.UpdateUtil.getUpdateMessage(UpdateUtil.java:74)
    05.03 19:15:15 [Server] WARN at us.myles.ViaVersion.update.UpdateUtil.getNewestVersion(UpdateUtil.java:91)
    05.03 19:15:15 [Server] WARN at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254)
    05.03 19:15:15 [Server] WARN at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440)
    05.03 19:15:15 [Server] WARN at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1512)
    05.03 19:15:15 [Server] WARN at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
    05.03 19:15:15 [Server] WARN at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
    05.03 19:15:15 [Server] WARN at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
    05.03 19:15:15 [Server] WARN at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
    05.03 19:15:15 [Server] WARN at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
    05.03 19:15:15 [Server] WARN at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1125)
    05.03 19:15:15 [Server] WARN at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:2023)
    05.03 19:15:15 [Server] WARN at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)
    05.03 19:15:15 [Server] WARN at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
    05.03 19:15:15 [Server] WARN javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
     
  12. @Mylescomputer
    Hi everytime I use the ./warp warpname, the client crash... on 1.8 AND 1.9...

    Please fix this. I use latest viaversion version
    All works great in the 0.5.2 version.


    Thanks
     
  13. What would be good is allowing 1.8 clients to join a 1.9 server.
     
    • Agree Agree x 1
  14. FormallyMyles

    Supporter

    This plugin will never support this, look into ProtocolSupport I believe they do it.
     
  15. minoneer

    Benefactor

  16. How do you get this error? I cannot recreate
     
  17. minoneer

    Benefactor

    That's an excellent question - I don't know what exactly is causing it. It randomly appears in the logs, usually after some players logget in / out.

    Since there are between 60 and 100 players on the server at any given time, it is almost impossible to track down. As the error occurs in the executor task, the stacktract isn't very helpful either.
     

Share This Page