Changes
- Fixed issues with removing holograms causing TPS drops
- Fixed Graves setting in weird spots or one block off around non solid blocks
- Fixed classes being finalized when they shouldn't be, which broke several methods
- Fixed configs not loading properly
Upcoming in future updates (around 4.9.10.1 that is confirmed)
- Multi Language Support (i18n) + Add help menu to the list
- Remove old events entirely or expand its removal date. Possibility it sticks around and remove its deprecation notice entirely for backwards compatibility for old plugins that rely on GravesX.
- Removal of Citizens (Use FancyNpcs instead)
- Mannequin support for 1.21.9+ servers as graves
Changes and Fixes
- Do not save default configs twice (was accidentally slipped back in when it shouldn't have been on plugin enable)
- Remove leftover debug info (during Folia Testing in 4.9.9.1 that was left over)
- Update dependencies for database types
- Fixed Libby import issues
⚠️ Notes
While 1.21.9 is being worked on, we have noticed bugs that have appeared around FileConfiguration.
We recommend staying up to date on these builds, as they are not the default versions on both providers and bugs may occur.
When using Java, we recommend the Adoptium JDK 17–21 for the best experience with this plugin.
Some users have had success using Java 22–25, but we have not tested on these versions — testing should be done as usual.
If changes need to be made to how configurations are handled, we will update to handle it properly.
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.eventsafter 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
GravesXAPIclass 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.
Its not a bug, its a feature >:(
🔧 Changes
- Introduced
actually-smite-death-location, which will behave as actual lightning - Deprecated ChestSort as the plugin is no longer maintained. The option remains, but will no longer receive support for using as a sorting option.
🔧 Changes
- Update Libraries
- Fix issue with nether-roof not spawning graves above nether roof when allowed
- Fixed SQLite issue with tables on startup
- Bumped config version (we noticed alot of people were using development builds, so this will bring in missing config options)
🆕 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
AIRin 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.





