• Added: 1.21.2 & 1.21.3 Compatibility
• Added: PacketEvents 2.6.0 Compatibility

Full Changelog: https://github.com/Bram1903/MinecraftPlayerCrasher/compare/v3.0.1...v3.0.2

Release Notes

• Fixed a bug where a player wasn't being registered when the client packet wasn't valid
• Changed the shadow plugin library to Gradle Up
• Some small improvements and refactoring

Full Changelog: https://github.com/Bram1903/MinecraftPlayerCrasher/compare/v3.0.0...v3.0.1

v3.0.0 Release Notes

I am happy to announce the release of version 3.0.0, which includes a major rewrite and restructuring of the project. This update makes the code largely platform-independent, requiring only a few platform-specific methods, as long as PacketEvents supports the platform. This version includes numerous bug fixes, adds proxy support, and introduces various enhancements.

Key Highlights

Proxy Support

The plugin now supports proxy servers. You can simply place the plugin in the proxy server's plugin directory, and it will manage all your backend servers. Additionally, you can execute the crash command at the proxy level, affecting players on backend servers.

1.21 Support

The plugin is now compatible with all versions from 1.8.8 to 1.21, including Bukkit, Spigot, Paper, Folia, and their forks, as well as Bungeecord, Velocity, and their forks.

Improved Messaging and Color Scheme

We have updated numerous messages and improved the overall color scheme for better readability and aesthetics. Previous issues with improper coloring of commands on Bukkit platforms and consoles have also been fixed.

New Commands

We have added /crashplayer and /bomb as aliases for the crash command. This addresses the issue where some hosts block the crash command from being executed in a terminal environment.

Known Issues

There are still some minor issues that need to be addressed. In certain cases, a player may be flagged as crashed, followed by a message indicating a failed crash attempt. This false detection is not harmful and will be fixed in a future patch.

On Velocity upon crashing a player an error is being thrown by Velocity a player has abruptly been disconnected, but because this is an error that is being thrown by Velocity automatically it's not something I can suppress or stop from happening.

For a detailed list of changes, please refer to the full changelog.

Changes

• Added: Brand Detector
• Added: Automatically using the best method based on the client's version
• Added: /crashinfo [player] which gives the client their brand and version.
• Improved: Hover Component after executing the crash command
• Fixed: Wrongly detecting when someone was crashed / not crashed
• Fixed: NullPointerException upon executing /crash

Full Changelog: https://github.com/Bram1903/MinecraftPlayerCrasher/compare/v2.4.0...v2.5.0

Changes

• Added: Support for 1.20.5 & 1.20.6 (we now support 1.8.8-1.20.6)
• Added: Proper crash detector thanks to jt for providing me with a good method
• Updated: PacketEvents from 2.2.1 -> 2.3.0
• Removed: FoliaScheduler, because it has been merged upstream into PacketEvents.

Full Changelog: https://github.com/Bram1903/MinecraftPlayerCrasher/compare/v2.3.1...v2.4.0