Tags
Creators
Details
2026.4.9.2
Compatibility
Changes
What's Changed
- Fixed Skript events breaking GravesX events.
- Improved debug logging for no-drop failures.
- Water and Lava Smart placement now properly respects configuration options.
- Improved grave saving during server shutdown.
- Moved non-grave world data messages behind debug mode.
- Added configurable Curse of Binding behavior.
- Improved Curse of Vanishing handling.
- Fixed MiniMessage compatibility with version 5+. (Direct Spigot compatibility may no longer work and may not be supported.)
- Fixed version checking when players join. (Development builds will display as development builds due to separate development and release profiles.)
- Improved void death handling so graves attempt to generate in a safe location.
- Updated ItemsAdder integration. (Currently untested as I do not own the plugin.)
- Updated dependencies.
- Improved MariaDB compatibility.
- Bumped the configuration version for the new release.
TL;DR: This update includes several reliability improvements for grave creation, shutdown handling, integrations, and item enchantment behavior.
Health & Development Update
I've been dealing with blood pressure issues that have resulted in several hospital visits since April. Since starting medication, I've also experienced periods where my blood pressure drops too low.
I'm still actively developing GravesX, and the project is not going unmaintained. Updates may simply be a little slower while I manage my health. GravesX remains open source, and contributors are always welcome to help with development.
Thank you for your patience and continued support.
Supplementary resources
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:vCFaodCy:OpYRNo98"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vCFaodCy:OpYRNo98"
}

