This update addresses the following bugs and changes:
- Moved off Authlib to Spigot API for head retrieval in
- 1.21.9 (legacy will still use authlib)
- Fixed issue with CompatibilityInventoryView (oops)
- Do not load graves if the world doesn't exist
- Grave Restoration is now disabled by default. You will need to enable it in grave.yml
Additions
- Added Folia Support (Integrations that don't have Folia support will not work at all. You will still need to use Spigot/Paper)
- Added Module Support (read documentation here)
- Graves that expire will now call
GraveExpiredEvent
- Added
GravePreTeleportEvent
(cancellable) - Added support for Toptal (formally hastebin) and pastebin as providers for Grave Dumps
- Added support for all particles and what you can do with them.
Changes
- Bump to 1.21.9
- Cleaned up unused methods
- Events have been moved to
dev.cwhead.GravesX.events
after re-working how events are handled. You can continue to usecom.ranull.graves.events
, but it has been marked as deprecated. - Packages made by me and JaySmethers have been relocated to their respected packages. Read Developer notes below.
- Changed the API structure. (old
GravesXAPI
class has been deprecated but you can still use the old API for now) - Fixed issue with Graves trying to poll every integration even though one had succeeded when creating a grave.
- Removed holograms that linger in the world. (this should be automatic, but in case they don't remove instantly, it will purge)
- Fixed a bug where entity graves would fail to generate.
To Developers
If your plugin hooks into GravesX, some methods were moved into their owning classes in this update. This can break code that imports the old packages — just update your imports to the new package locations and everything should work again. Code changes were not made so previous code should work just fine.
🆕 Additions
- GraveEconomyEvent – Allows someone to modify the economy amount for your own plugins.
- GravePistonExtendEvent – Fires when a piston extends and breaks a grave
- Nexo Support – (Deprecated Oraxen. Though we have made changes to fix some issues in Oraxen, we no longer plan to maintain support nor will provide support going forward and recommend switching to Nexo. See here)
- Lightning Strike upon death (Disabled by default)
- Explosion effect on looting grave (Disabled by default)
- Databases – Now can have configured table prefixes
You will need to alter your database tables or your server will start with no graves data.
🔧 Changes
- Deprecated FurnitureEngine
Recommend using FurnitureLib as an alternative. Kept in the code for servers that still use it, but we dropped support for FurnitureEngine.
- Updated Skript Integration to work on newer versions
- Updated PostgreSQL integration to patch CVE-2025-49146
- Fixed H2 breaking in certain conditions
- Updated commons-lang3 to patch CVE-2025-48924
- Fixed issue where putting
AIR
in the recipe would cause plugin errorsAlthough we’ve previously stated this should be blank, this update resolves that edge case.
- Fixed exploit where grave items duplicated upon server shutdown
- Updated Kyori and fixed a bug where hex colors didn’t work in obituaries
- Bedrock names in GeyserMC are now validated
Java users could previously have the same username even with the prefix being before the name.
- Fixes in the API for grave creation
If time isn’t configured, it will now revert to the config's set time.
🙏 Special Thanks
Big thanks to @JaySmethers and @Going for helping with this update.
Also thanks to the Nexo Developer for assistance in safely adding and removing their furniture
(they previously worked on Oraxen as well).
🛠️ Development Announcement and Future of the Plugin
This version took a while to release.
Reason: I was contracted to do Redbox removals in my area and didn’t have time to release updates.
We hope this update was worth the wait during that absence.
Huge thanks to @JaySmethers for fixing many of the bugs.
With the codebase being over 3 years old, we’ve made countless line changes and retained Ranull’s codebase,
but modern Minecraft versions have introduced lingering bugs that may only be fixed by a complete re-write.
We are planning a full rewrite for version 5.0.1.0.
Until then:
- We will continue supporting the 4.9 codebase with patches.
- Development of 5.0.1.0 will happen in parallel.
- Timeline: Could take months or even years — we don’t know yet.
- We’ll make a new GitHub branch for testing and decision-making for features going forward.