If you’re running 1.14, use the latest dev build.
If you’re running 1.8 through 1.13, use the latest release.
If you’re running 1.7 or below, use the 3.7.0 release.

Thanks for over 400k downloads everyone!

If you love ProtocolLib or it has made your life significantly easier, consider donating or leaving a positive review below. It really means a lot!

Certain tasks are impossible to perform with the standard Bukkit API and may require working with and even modifying Minecraft directly. A common technique is to modify incoming and outgoing packets or to inject custom packets into the stream. This is quite cumbersome to do, however, and most implementations will break as soon as a new version of Minecraft has been released, mostly due to obfuscation.

ProtocolLib is a library that allows read and write access to the Minecraft protocol. It handles most of the overhead required with reflection and channel injection and provides wrappers to simplify packet modification. It is updated with most Minecraft updates so, ideally, individual plugins don’t have to. ProtocolLib often doesn’t need to be updated for minor updates, especially if there are few code changes (i.e. the 1.8 security updates)

Useful Links

Before reporting a bug:

  • Look for an update for ProtocolLib, there’s a good chance your error or bug has already been fixed.
  • Read the stack trace and make sure it’s an error with ProtocolLib. ProtocolLib’s package is com.comphenix.protocol. If you don’t see that anywhere, it’s not ProtocolLib.

When reporting a bug:

  • I’d prefer it if you used the issue tracker, but you can also do this in the discussion section. Don’t report bugs in the reviews.
  • Provide as much information as possible. Provide your ProtocolLib version and Spigot version.
  • Provide any stack traces or “errors” using pastebin.

For server operators
Just download ProtocolLib from the link above. It doesn’t do anything on its own, it simply allows other plugins to function.

For developers
A comprehensive tutorial can be found here.

There is a lightweight alternative to ProtocolLib called TinyProtocol. It is essentially a mechanism to send and receive raw packets without structure modifiers or wrappers. It can be found here.

Maven repository
If you’re using Maven, you’ll be able to automatically download the jar, JavaDoc and associated sources from the following repository:

<!– And so on –>


Code (Java):
repositories {
maven { url “” }

Then add it as a dependency like so:

<!– And so on –>


Code (Java):
dependencies {
compileOnly group: “com.comphenix.protocol”, name: “ProtocolLib”, version: “4.4.0”;

Developers are encouraged to use the ProtocolLib module as a dependency as of version 4.4.0. ProtocolLib-API was a fun experiment, but had some unfortunate linkage errors.

Main administrative command. Supports the following sub-commands:

  • config: Reload the configuration file.
  • check: Check for new versions on BukkitDev.
  • version: Displays the currently running version of ProtocolLib.
  • timings: Toggle measuring the amount of CPU time spent by each plugin.
  • listeners: Display what plugins are using ProtocolLib, and the packet types they are intercepting.

Logs hex representations of the provided packets to a file or to console
Syntax: /packetlog <protocol> <sender> <packet> [file/console] Accepted packets can be found here.

All of these commands require the permission protocol.admin.

A small set of configuration options are available:
Global section

Code (YAML):
auto updater.notify: true #Inform any player with the permission when a new version of ProtocolLib is out.
auto false #Automatically download and install the newest version of ProtocolLib. The installation will take effect when the server restarts.
auto updater.delay: 43200 #The number of seconds between each check for a new update.
auto updater.last: 0 #This simply records the last time (in seconds since 01.01.1970) an update check was performed. Set it to 0 to force a new update check.
metrics: true #If TRUE, ProtocolLib will publish anonymous usage data to Set it to FALSE to opt-out.
background compiler: true #If TRUE, ProtocolLib will try and improve performance by replacing reflection with compiled code on-the-fly.
ignore version check: None #Force ProtocolLib to start for a specified Minecraft version, even if it is incompatible.

One of the main goals of this project was to achieve maximum compatibility with CraftBukkit. And the end result is quite flexible. Aside from package changes, it should be resilient against future changes. It’s likely that I won’t have to update ProtocolLib for anything but bug fixes and new features.

How is this possible? It all comes down to reflection in the end. Essentially, no name is hard coded – every field, method and class is deduced by looking at field types, package names or parameter types. It’s remarkably consistent across different versions.

ProtocolLib collects statistics anonymously through MCStats. Participation is completely optional and you can opt-out at any time, although it is really helpful in figuring out what environments the plugin is running in (i.e. versions of Spigot, Java, and ProtocolLib), so I can adjust development accordingly.

If ProtocolLib has made your life significantly easier or you’re feeling particularly generous, consider donating! It’s a great way to support the many hours I’ve spent maintaining this plugin and keeps me motivated. Don’t donate if you can’t afford it.


Huge thanks to those who have donated! :)
(If I missed you or you want to remain anonymous, shoot me a PM)

  • nathan818 – $1000
  • MineCove – $100
  • joehot200 – $75
  • Techcable – $30
  • VintageDon – $25
  • games647 – $25
  • Photon – $15
  • snapsi – $5
  • Aberzhulan – $5
  • Art in the Shade – $5

Please don’t leave bug reports in the reviews section. It’s the single worst place to get support. Use the issue tracker, where I can actually diagnose and fix your issue.

Leave a Reply

Your email address will not be published. Required fields are marked *

13 + 16 =

Skip to toolbar