ProtocolLib
ProtocolLib
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.
Links
Support
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 issue tracker. 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.
FAQ
- Why do I get FieldAccessExceptions when I try to read or write from packets?
Quote: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.
Examples
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 Maven Central. You can add it as a dependency like so:
<dependencies> <dependency> <groupId>net.dmulloy2</groupId> <artifactId>ProtocolLib</artifactId> <version>5.4.0</version> </dependency> <!-- And so on --> </dependencies>
Commands
Protocol
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.
Example:
/protocol update
Packet
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):
- Connection side: Either client or server.
- Multiple ID ranges: Can be a single packet ID like 14, or a range like 10 - 15. Defaults to 0 - 255 if not specified.
- Detailed: If TRUE, prints the full packet content.
Example:
/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.
Filter
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.
Configuration
A small set of configuration options are available:
Global section
| Option | Default |
Description |
|---|---|---|
| auto updater.notify | true | Inform any player with the permission protocol.info when a new version of ProtocolLib is out. |
| auto updater.download | true | 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 mcstats.org. 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. |
| suppressed reports | None | If 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.
Compatibility
One of the main goals of this project was to achieve maximum compatibility with Minecraft. And the end result is quite good, 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.
(note that the below list hasn't been updated in ages and ymmv)
Plugins that appear to be compatible
Plugins known to be compatible
- SpoutPlugin
Plugins using ProtocolLib
- Orebfuscator
- TagAPI
- DisguiseCraft
- VanishNoPacket (v3.18.5 and earlier)
- BkCommonLib
- CraftBook
- ChairsReloaded (3.0.2 and earlier)
- Scavenger
- TabAPI
- Individual-Signs
- ItemRenamer
- RandomCoords
- AntiCommandTab
- Sneaky
- Spy
- Statues
- Seasons
- Safe Command Block
- PlayerHider
- Phantasma Chat Filter
- Ghost Hunt
- ReMap
- AttributeHider
- uCars
- uPlanes
- PropHunt
- Portable-Horses
- ClickEdit
- RageBan
- ReChat
- PlayEffect
- FakePlayers
- PlayerCountMessage
- Vampire
- Murder
- NoSpy
- PingNachricht
- NoCheatPlus
- ScoreboardStats
Inactive projects
Please let me know if you want me to add your plugin to this list. :)
Privacy
This plugin uses BStats 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.
Donating
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. :)
Note: Create an issue if you're having problems. I generally don't check the BukkitDev comments.
-
View User Profile
-
Send Message
Posted Mar 21, 2014@libraryaddict
I'm not sure I follow - monitor listeners are a special case, and are allowed to see filtered packets send by other plugins. But, they're not supposed to cancel or change those packets. In fact, doing so regardless causes weird behavior due to optimizations in ProtocolLib.
For instance, monitor listeners will be able to change (and cancel) ordinary packets, but they cannot prevent filtered packets from going through. This is because the cancelled state and packet variable is completely ignored when dealing with filtered packets:
But I have considered reworking the filter system. Most plugins don't actually need to bypass every packet listener, just their own, so it might be better for packet listeners to just do the filtering themselves.
One idea is to extend PacketEvent with a token field, which is set by a parameter in sendServerPacket() and recieveClientPacket(). Or perhaps a "plugin sender" field, although that would require dynamically detecting the calling plugin, which is likely slower and less reliable. A third possibility would be to replace "filter" with a generic Predicate, and allow arbitrary packet listeners to be skipped that way.
I'll need to think about this.
@libraryaddict
Unfortunately, there's only two real possibilities:
So - this might call for a new feature as well. I'm thinking I could add a general "post" handler to PacketEvent that gets executed when a packet has been successfully sent. Or, it could be a "listenable future" you register a callback on.
I see if I can't get something done tomorrow. Let me know if you have any suggestions.
-
View User Profile
-
Send Message
Posted Mar 21, 2014Question. How would I send a packet, inside another packet event?
So if I am catching the entity spawn packet. But want to send another packet straight away.
How would I go about that?
Sending the packet directly inside the listener, from what I've seen makes the 2nd packet be sent first. And the original packet is delayed.
Using a scheduler does work, but delays it by a tick where i want it to be sent directly after the current packet.
-
View User Profile
-
Send Message
Posted Mar 20, 2014@aadnk
Just made sure I was running the latest, and added output to my packet listener.
No go.
Its catching the disguise packets sent by my other plugin. Lib's Disguises
Thats using ProtocolLib.getProtocolManager().sendServerPacket(player, packet, false);
-
View User Profile
-
Send Message
Posted Mar 20, 2014@flatbmx
Yup, there haven't been any significant internal changes.
@libraryaddict
Monitor listeners should catch those - are you using an old development version perhaps?
-
View User Profile
-
Send Message
Posted Mar 19, 2014Is there a way you can catch a packet which is being sent with filtering set as false?
Monitor makes sense as catching all packets, but it doesn't.
Using the /packet command does not return any output either.
-
View User Profile
-
Send Message
Posted Mar 19, 2014Just making sure, latest build 3.2.0 is stable for 1.7.5 aswell? Says for version 1.7.2
-
View User Profile
-
Send Message
Posted Mar 17, 2014@tomori_peti
I do support MCPC+ 1.6.4 and earlier, to some extent. The trouble it, it's difficult to reproduce any reported issues, as they often depend on the combination of mods and plugins that have been installed.
I don't support MCPC+ 1.7.4 at the moment though, but it could theoretically be implemented if enough people requested it.
-
View User Profile
-
Send Message
Posted Mar 16, 2014Does MCPC+ something you want to support?
-
View User Profile
-
Send Message
Posted Mar 15, 2014@aadnk
Just did it works perfectly on the other server aswell, thanks! :)
-
View User Profile
-
Send Message
Posted Mar 14, 2014@erik75125690
Have you added the depend directive in your plugin?
-
View User Profile
-
Send Message
Posted Mar 14, 2014@aadnk
I made a server that only had the plugin I made with ProtocolLib and the ProtocolLib and there it worked fine.. I used the exact same craftbukkit build.
-
View User Profile
-
Send Message
Posted Mar 13, 2014@erik75125690
Have you installed ProtocolLib?
Also - see if you can't find another exception earlier in the console log - perhaps ProtocolLib crashed before it could be loaded?
-
View User Profile
-
Send Message
Posted Mar 13, 2014I get this error... http://gyazo.com/b8f4f95ccbc78b235fa850b06582b679
-
View User Profile
-
Send Message
Posted Mar 7, 2014@Nickbbeezy
I created a ticket from your comment. Could you elaborate a bit on your current setup in that ticket (plugins, server), so that I have a way of reproducing your issue.
-
View User Profile
-
Send Message
Posted Mar 6, 2014After upgrading to Build #218, experienced some issues on login with being unable to type & move. GUIs closed automatically when opened and player is moved back to login location when trying to move. Fixed by downgrading to 3.2.0 RB.
-
View User Profile
-
Send Message
Posted Mar 1, 2014@aadnk
Hi aadnk, yes... you were right. It is some other plugin. I don't know which one yet. Thank you for getting back to me. It is working great!
-
View User Profile
-
Send Message
Posted Feb 26, 2014@catprowler
Does this happen in every world, and generally in every location?
Still, I don't believe neither ServerSigns nor Vault uses ProtocolLib, so it must be caused by some other plugin. Could you give the the output (pastebin) of the command "protocol listeners"?
-
View User Profile
-
Send Message
Posted Feb 26, 2014Hi there, I just noticed something strange with the dev build 3.3.0 ... when I use it, it will not let me place down any signs or use any command set on the signs from serversigns. When I switched it back to the 3.2.0 version it worked fine. I just thought I would mention it. Thank you.
-
View User Profile
-
Send Message
Posted Feb 23, 2014@timgeel
Did you restart the server completely after updating ProtocolLib? Reloading is usually not sufficient when you upgrade plugins.
As for changing the difficulty dynamically and per-player - take a look at the respawn packet. Of course, that will only change the apparent difficult, you have to implement some logic on the server-side to make it complete (such as banning the player).
-
View User Profile
-
Send Message
Posted Feb 22, 2014@aadnk
Thx, no more errors, all works fine