Skip to content

Instantly share code, notes, and snippets.

@phit phit/updatenetty.md
Last active Jul 14, 2019

Embed
What would you like to do?

Updating netty manually for Minecraft 1.12

Get your minecraft_server.1.12.2.jar from the root of your server, download the latest netty full package http://dl.bintray.com/netty/downloads/netty-4.1.37.Final.tar.bz2

Open your server jar with 7zip and navigate to minecraft_server.1.12.2.jar\io\netty\

open the netty package you downloaded and go to netty-4.1.37.Final.tar.bz2\netty-4.1.37.Final.tar\netty-4.1.37.Final\jar\all-in-one\netty-all-4.1.37.Final.jar\io\netty\

back in the minecraft server jar delete these 6 folders

now simple copy the same 6 folders from the netty package into the minecraft jar

throw the jar back into the root of your server and you are done!

@chaos234

This comment has been minimized.

Copy link

commented Jul 23, 2018

Could you explain please what this will change for the current downloaded 1.12.2 server version and will this patch added to 1.12.2 and change it maybe to 1.12.3?

Would be nice to know because what whill happen if smth. goes wrong? Safte first ;)

Edit: What about the client side version? Anything to edit here to not run into any conflicts?

@phit

This comment has been minimized.

Copy link
Owner Author

commented Nov 19, 2018

Could you explain please what this will change for the current downloaded 1.12.2 server version and will this patch added to 1.12.2 and change it maybe to 1.12.3?

Not quite sure what you are trying to say, this simply updates the included netty version for issues like:
repeated spam of this and frequent disconnects
NetworkDispatcher exception io.netty.channel.unix.Errors$NativeIoException: syscall:writev(…) failed: Broken pipe

It doesn't touch any Mojang code.

Would be nice to know because what whill happen if smth. goes wrong? Safte first ;)

Always take backups, but if you mess this up the server probably doesn't even start and you can just download a clean minecraft_server jar file.

Edit: What about the client side version? Anything to edit here to not run into any conflicts?

No the client doesn't care, and software like Spigot and Bungeecord already do this on their side. Forge is the outlier in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.