ProtocolLib has, for the most part, moved over to Spigot! If you need support, head over there!

Certain tasks are impossible to perform with the standard Bukkit API, and may require working with and even modify Minecraft directly. A common technique is to modify incoming and outgoing packets, or 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.

Critically, different plugins that use this approach may hook into the same classes, with unpredictable outcomes. More than often this causes plugins to crash, but it may also lead to more subtle bugs.

Development builds of ProtocolLib can be found here:
Older development builds can be found here:
These builds have not been approved by the BukkitDev staff. Use them at your own risk.


Please create a issue with as much information as possible if you experience a problem that has not already been reported. Comments with a huge stack trace will be deleted.

If you need help with the API, please use the Spigot discussion forum. If your question cannot be made public for whatever reason (including security bugs), send me a personal message instead.

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.


  • Why do I get FieldAccessExceptions when I try to read or write from packets?

The reason for these exceptions is because ProtocolLib is not using the packet format as described on the Wiki, it's using the in-memory representation of these packets. Often, the in-memory representation will use integers instead of shorts and bytes, and store more complex objects (like ItemStacks) directly.

You can figure out the in-memory representation from the Minecraft source code, or just use PacketWrapper where I've done all that work for you.


Source code for a bunch of example programs that use ProtocolLib can be found at this thread on the main support forum.

You may also be interested in PacketWrapper, a library that makes it possible to modify a packet without having to decompile the Minecraft source code.

Finally, for the more advanced users who want to use ProtocolLib if present, but still fall back on their own packet listening system, I recommend taking a look at this thread. I explain where and how to inject code into CraftBukkit in order to intercept sent and received packets yourself.

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 -->

This repository contains ProtocolLib, TagHelper and BlockPatcher. You can add any of them as a dependency like so:

  <!-- And so on -->



Main administrative command. Supports the following sub-commands:

  • config: Reload the configuration file.
  • check: Check for new versions on BukkitDev.
  • update: Check for new versions and automatically download the JAR. The server must be restarted for this to take effect.
  • timings: Toggle measuring the amount of CPU time spent by each plugin. See here for more information.
  • listeners: Display what plugins are using ProtocolLib, and the packet types they are intercepting.

All of these commands require the permission protocol.admin.


/protocol update


Add or remove a debug packet listener. This is useful for plugin authors who just wants to see when a packet is sent, and with what content.

Sub commands:

  • add: Add a packet listener with a given packet ID.
  • remove: Remove one or every packet listener with the given packet IDs.
  • names: Print the name of every given packet ID.

Parameters (in order):

  1. Connection side: Either client or server.
  2. Multiple ID ranges: Can be a single packet ID like 14, or a range like 10 - 15. Defaults to 0 - 255 if not specified.
  3. Detailed: If TRUE, prints the full packet content.


/packet add client 10-13 true

For 3.0.0 and above, you should specify the protocol, sender and name instead:

/packet add play server chat true

In 3.4.0-SNAPSHOT and above, you can also display the packet before its modified by any packet listeners:

/packet add play server chat compare

Remove all listeners:

/packet remove client
/packet remove server

Note that this command should rarely be used on a production server. Listening to too many packets may crash the server.


The filter system (introduced in 2.4.1) uses the built in JavaScript interpreter in JVM 6 (Rhino) to extend the packet command with filtering capabilities - it is now possible to, say, only print entity metadata packet events (packet add server 40) for a given entity ID:

> packet add server 40 true
Added listener ListeningWhitelist{priority=MONITOR, packets=[40]}
> filter add entity_filter 40
Enter filter program ('}' to complete or CANCEL):
function(event, packet) {
>   return packet.a == 1000; 
Added filter entity_filter.

This should be much more convenient than having to compile a test plugin and reload the whole server. Note that this feature is disabled by default for security reasons. To enable it, add "debug: true" to config.yml.


A small set of configuration options are available:

Global section



auto updater.notifytrueInform any player with the permission when a new version of ProtocolLib is out.
auto updater.downloadtrueAutomatically download and install the newest version of ProtocolLib. The installation will take effect when the server restarts.
auto updater.delay43200The number of seconds between each check for a new update.
auto updater.last0This 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.
metricstrueIf TRUE, ProtocolLib will publish anonymous usage data to Set it to FALSE to opt-out.
background compilertrueIf TRUE, ProtocolLib will try and improve performance by replacing reflection with compiled code on-the-fly.
ignore version checkNoneForce ProtocolLib to start for a specified Minecraft version, even if it is incompatible.
suppressed reportsNoneIf any error or warning report is present in this list, they will not appear in the console or the log.

For more information, take a look at the default configuration file.

Tutorial for developers

See this page for more information.


One of the main goals of this project was to achieve maximum compatibility with CraftBukkit. And the end result is quite good - in tests I successfully ran an unmodified ProtocolLib on CraftBukkit 1.8.0, and it should be resilient against future changes. It's likely that I won't have to update ProtocolLib for anything but bug and performance fixes.

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.

Plugins that appear to be compatible

Plugins known to be compatible

  • SpoutPlugin

Plugins using ProtocolLib

Inactive projects

Please let me know if you want me to add your plugin to this list. :)


This plugin uses MCStats to generate and publish anonymous aggregate usage statistics, but you can easily opt-out by setting metrics in config.yml to false.

If enabled, the following is sent every ten minutes:

  • Metrics revision version (currently 6).
  • Server's GUID
  • Players currently online (not max player count)
  • Server version string (the same version string you see in /version)
  • Current version of ProtocolLib
  • The name of every plugin that registers a packet listener in ProtocolLib.


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.


I would like to thank everyone who has donated to ProtocoLib on BukkitDev. I really appreciate it. :)


ProtocolLib Statistics

Note: Create an issue if you're having problems. I generally don't check the BukkitDev comments.

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Sudding123 Sudding123 Nov 11, 2013 at 01:00 UTC - 0 likes

    I have plobrem with spigot 1.7 looks like it only spam when players log in

  • Avatar of aadnk aadnk Nov 10, 2013 at 22:04 UTC - 0 likes

    @PhanaticD: Go

    There should at least be some text after Caused by: java.lang.ClassCastException at the end, if not a couple of extra lines. If not, something has gone terribly wrong in the Bukkit logger.

  • Avatar of PhanaticD PhanaticD Nov 09, 2013 at 23:18 UTC - 0 likes

    there wasnt anything after

  • Avatar of aadnk aadnk Nov 08, 2013 at 22:54 UTC - 0 likes

    @Sirse: Go

    It should be up now. My previous hosting provider deleted my virtual server, so I decided to switch to a different host.

    @PhanaticD: Go

    Could you show me the next ten lines in your console? You've cropped out the most important part of the stack trace - the original exception.

  • Avatar of PhanaticD PhanaticD Nov 08, 2013 at 21:15 UTC - 0 likes

    I have this problem with protocollib and 1.7 spigot

  • Avatar of Sirse Sirse Nov 08, 2013 at 06:32 UTC - 0 likes

    What's happend with Jenkins build server?

  • Avatar of craftik7 craftik7 Nov 07, 2013 at 11:03 UTC - 0 likes

    @aadnk: Go

    I have problem with ProtocolLib on Spigot 1.7 and my plugin:

  • Avatar of Quantum64 Quantum64 Nov 05, 2013 at 01:07 UTC - 0 likes

    @aadnk: Go

    I put up a pull request on your Packet Wrapper GitHub, it makes entity metadata much more comprehensive to modify, as I posted below, I found it quite complicated before.

    Last edited Nov 05, 2013 by Quantum64
  • Avatar of aadnk aadnk Nov 03, 2013 at 16:30 UTC - 0 likes

    @jet315: Go

    Don't post stack traces in the comments. At the very least, use pastebin if you insist on using comments instead of the ticket system. I'll be forced to delete your comment if you don't.

    As for your problem, have you tried deleting the plugins/ProtocolLib folder?

  • Avatar of aadnk aadnk Nov 03, 2013 at 02:42 UTC - 0 likes

    @Quantum64: Go

    You can get an overview of all the different metadata properties here. If I'm not mistaken, you only need to send a single key-value pair for the client not to crash (preferably index 0):

    You can also get the WrappedDataWatcher from an entity with WrappedDataWatcher.getEntityWatcher(entity), and send that instead.