Before installing a plugin, use the official website to confirm that the plugin supports your server software and Minecraft version.
What is PacketEvents?
Modern packet library used by plugins that need cross-version protocol access. MSH lists it as a mainstream option in Core & Management , but the official project documentation remains the source of truth for exact builds, dependencies and current compatibility.
| Developer / maintainer | retrooper and contributors |
|---|---|
| Category | Core & Management |
| Pricing | Free |
| Typical platform | Paper-family servers |
| Primary use | Modern packet library used by plugins that need cross-version protocol access. |
What it is good at
- Packet event API across multiple Minecraft server/proxy platforms
- Common foundation for anti-cheats and protocol-aware plugins
- Designed to avoid each plugin reimplementing packet handling
What types of servers should consider it?
- Servers using plugins that require PacketEvents
- Plugin developers working with the Minecraft protocol
Pricing and distribution
The plugin is distributed as a free option. Check the official page for the current download source and license.
What to check before using it
- Use the version required by the plugins depending on it; a packet library mismatch can break dependent plugins.
Also check the plugin's current dependency list, migration notes and supported server versions on the official page before changing a production server.
Operational caution: PacketEvents is an API/library for other plugins; it does not automatically block cheats or translate client versions. A dependency failure can disable an otherwise correctly installed plugin.
Common questions
What does PacketEvents do?
Modern packet library used by plugins that need cross-version protocol access.
Is PacketEvents a plugin or a mod?
PacketEvents is listed here because it is used as a server plugin in its supported plugin environment. Some projects also publish builds for other platforms; use the official download page to choose the correct platform build.
Do players need to install it?
Most server plugins run server-side and do not require players to install the same JAR. Features that rely on resource packs, Bedrock bridges or optional client integrations can still change what the player must download or accept.
How do I install it?
Choose the prebuilt PacketEvents artifact for the platform running it (such as Paper, Velocity or BungeeCord) and install the version required by the plugins that depend on it. Do not assume one JAR works on every platform.
How do I know the plugin loaded?
After a complete restart, inspect startup logs for PacketEvents initialization and ensure each dependent plugin enables without missing-class or incompatible-API errors. Run a functional test of the dependent anti-cheat or protocol feature.
What if it does not load?
If packet handling breaks after an update, record the server and PacketEvents versions and compare with the dependent plugin’s declared API range. Revert both to a known working pair on a test copy before changing packet settings.
For general plugin installation, read How to Install Plugins on a Minecraft Server. To understand the plugin lifecycle and how plugins differ from mods, read How Minecraft Server Plugins Work. If the plugin refuses to load, use Plugin Failed to Load.
Alternatives
References
Plugin versions, pricing and platform support can change. These project pages were used as the primary references for this overview.
Related MSH pages
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.