Universal ViaBackwards 4.0.1

Allow older versions to connect to your Minecraft server.

  1. Matsv submitted a new resource:

    ViaBackwards - Allow Minecraft 1.9.x on your 1.10.x server.

    Read more about this resource...
     
    • Like Like x 1
    • Winner Winner x 1
  2. nice idea, this plugin will probably be useful to a lot of people.
     
    • Agree Agree x 1
  3. I have a problem. When I'm joining 1.10 server with 1.9 client I'm kicked from the server and it writes me "Disconnected". In console there is an error "
    nick lost connection: Internal Exception: io.netty.handler.codec.EncoderException: java.lang.RuntimeException: An internal error occured.
    "
    Console log when I start the server
    Code (Text):

    [13:49:59] [Server thread/INFO]: [ViaVersion] Loading ViaVersion v0.9.8
    [13:49:59] [Server thread/INFO]: [ViaVersion] ViaVersion 0.9.8 is now loaded, injecting!
    [13:49:59] [Server thread/INFO]: [ViaBackwards] Loading ViaBackwards v1.0
    [13:49:59] [Server thread/INFO]: [ProtocolLib] Loading ProtocolLib v4.0.2
    [13:49:59] [Server thread/INFO]: [ViaBackwards] Enabling ViaBackwards v1.0
    [13:49:59] [Server thread/INFO]: [ProtocolLib] Enabling ProtocolLib v4.0.2
    [13:49:59] [Server thread/INFO]: [ProtocolLib] Started structure compiler thread.
    [13:49:59] [Server thread/WARN]: **** SERVER IS RUNNING IN OFFLINE/INSECURE MODE!
    [13:50:00] [Server thread/INFO]: [ViaVersion] Enabling ViaVersion v0.9.8
     
     
  4. Can you set debug=true in server.properties and give me the full error after restarting the server?
     
  5. I am also kicked when I attempt to join my server on 1.9.
     
  6. Thanks for reporting, will create a fix when I'm back home
     
    • Like Like x 2
  7. @BaronOrg @love_geo_jasiu98 This was actually an issue in ViaVersion. I created a patch for it. You can use the devbuild on our buildserver until it's released on Spigot. (Direct download link)
     
    • Friendly Friendly x 1
  8. After uploading that version to my server I can join, however whenever a new block is sent to the client it disconnects them.
     
  9. I don't have this issue, could you give me some more information:

    • The exception from the console. (If there is none, enable debug=true in your server.properties)
    • The disconnect message
    • Minecraft version you used to login
    • what block did you try to place
    • What plugins do you use

    Thanks
     
    #10 Matsv, Aug 8, 2016
    Last edited: Aug 8, 2016
  10. Ah, I'm not handling wrong metadata correctly, thanks for reporting :).
    Looks like you are using an outdated plugin that still sends 1.8-9 metadata. Make sure you update all of them.
     
  11. Alright. Will you be making it so that you do handle wrong metadata or not?
     
  12. Yes I will handle it that you don't get kicked because of ViaBackwards. But sending wrong metadata could also affect things client-sided, breaking stuff, crashing clients etc. I won't handle those things.
     
    #14 Matsv, Aug 8, 2016
    Last edited: Aug 8, 2016
  13. Matsv updated ViaBackwards with a new update entry:

    v1.0.1 - Handle metadata errors

    Read the rest of this update entry...
     
  14. What is the benefit of this over protocolsupport?
     
  15. Lightweight, support for Spigot 1.10, Correct sounds, compatible with multiple server versions in the future due to the design of ViaVersion. Other than that not that much. I created this as a project for my server and shared it, since it might be useful for others.
     
  16. Awesome I might use it then. Thanks for contributing; more choice is always better.
     
    • Like Like x 1
  17. This looks awesome! :) I'll consider using this.
     
    • Like Like x 1
  18. What about allowing 1.8 clients aswell?
     
    • Informative Informative x 1