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 Dec 12, 2013Finally! v3.0.1 for 1.7.2! :D
-
View User Profile
-
Send Message
Posted Dec 11, 2013Hey again, huge thanks for helping out AntiCommandTab! Anyhow, I don't know if you're aware, but I believe ProtocolLib #176 is blocking first logins. Someone can attempt to join, but eventually get this error. If they disconnect at that point, and rejoin, they can connect. If you reload/restart, then they'll have their first login denied. There's no stack trace in the console, and I've tested on both Spigot and Craftbukkit and it yields the same result.
Thanks
-
View User Profile
-
Send Message
Posted Dec 11, 2013@aadnk
Thank you.
-
View User Profile
-
Send Message
Posted Dec 11, 2013@fungreenfox
I haven't, and I can't. Only mods can delete tickets. I suspect the server/database might have been overloaded, and lost your ticket.
But as for your problem, it's already been reported and fixed (in TagAPI).
-
View User Profile
-
Send Message
Posted Dec 11, 2013I want to know, why you have deleted my ticket about a protocollib error, and without telling me?
My console is constantly spamming this. http://dev.bukkit.org/paste/8979/
-
View User Profile
-
Send Message
Posted Dec 10, 2013@lilacorn
Please post these errors, either here with pastebin, or in a ticket. Also, keep in mind that both TagAPI and BKCommonLib will fail in 1.7.2 with ProtocolLib.
@winter4w
ProtocolLib 2.7.3 does not support 1.7.2. You need to either use the version on the Jenkins server, or wait until ProtocolLib 3.0.0 has been released on BukkitDev.
@stgram
This is caused by TagAPI. You can get a fixed version on my Jenkins server.
@THEREDBARON24
Yes, the Jenkins server is here. Please note that the builds have not been approved by the BukkitDev staff. Use them at your own risk.
-
View User Profile
-
Send Message
Posted Dec 10, 2013Every time I put this plugin back on I get random massive netty issues.When I don't have it in my server, I dont get the netty errors.
-
View User Profile
-
Send Message
Posted Dec 10, 2013this error on the dev one!!!!!
-
View User Profile
-
Send Message
Posted Dec 10, 2013I've no idea if it is yours or bergkiller's plugin.... http://pastebin.com/CFwVjT1K
-
View User Profile
-
Send Message
Posted Dec 10, 2013Im sorry, but I dont see a link for the unofficial builds...Can someone point me in the right direction?
-
View User Profile
-
Send Message
Posted Dec 10, 2013@joda17
I didn't even known people were still using it. :P
I did a quick update just now. You can get version 1.4.1 on my Jenkins server.
-
View User Profile
-
Send Message
Posted Dec 10, 2013@aadnk When BlockPatcher will be update?
-
View User Profile
-
Send Message
Posted Dec 10, 2013@aadnk Great job on getting an update! So many changes to bukkit... so many deprecations...
-
View User Profile
-
Send Message
Posted Dec 9, 2013@PhanaticD
Oh! I forgot to check tickets, how silly of me. We posted nearly at the same time too!
-
View User Profile
-
Send Message
Posted Dec 9, 2013@Swords761
http://dev.bukkit.org/bukkit-plugins/protocollib/tickets/164-index-out-of-bounds-exception/
-
View User Profile
-
Send Message
Posted Dec 9, 2013@aandk:
Thanks for all your hard work on ProtocolLib! In the interest of finding errors for you with 1.7.2, I've been getting this IndexOutofBounds error constantly spamming my console. It seems harmless, but it's quite annoying:
http://pastebin.com/NLi9cAsA
Apologies if this was already reported! I did a quick check of the comments but didn't see anything. I'm running Spigot #1173.
-
View User Profile
-
Send Message
Posted Dec 9, 2013на 1.7.2 пойдет?
-
View User Profile
-
Send Message
Posted Dec 8, 2013Your title here... ===3.0.0 is fine excepting the damn message that always shows up
-
View User Profile
-
Send Message
Posted Dec 8, 2013@gustebeast
I'm sure shaders are client-side only as it is an ingame, graphics-related option you can alter via the game-menu. The server, no matter how much functionality it may have, can never alter anything strictly client-side without some sort of corresponding client mod. Unless Mojang changed something about client-server interactions, having the server being able to force shaders would be like having the server being able to force texture packs, or change volume, or change the graphics setting from "Fast" to "Fancy", all of which aren't currently possible.
-
View User Profile
-
Send Message
Posted Dec 8, 2013@gustebeast
Look at the unofficial protocol documentation. There's no mentions of shaders anywhere, nor would I expect it to - shaders are currently experimental.