Tags
Creators
Details
2.7.2
Compatibility
Changes
betterGraveStones 2.7.2
This version includes several technical improvements, bug fixes, and new optional Locator Bar features.
Added
- Optional support for the vanilla Locator Bar on Minecraft/Paper 1.21.6+
- Grave waypoints can optionally be shown in the Locator Bar
- Reserved grave waypoint colors:
- Gray for normal grave markers
- Gold for nearby/own grave markers
- Player waypoints can optionally use UUID-based colors
- Optional animated UUID color gradients for player waypoints
- Admins can toggle whether they want to see all grave waypoints
- Stored offline players can now be used and tab-completed in commands
Changed
- Normal players should only see their own graves by default
- Admin visibility for all graves is optional and not permanently enabled
- Locator Bar command output can now be suppressed through the config
- MySQL connection handling is now more robust against idle timeouts
- Storage and plugin lifecycle handling has been cleaned up
- Internal code structure has been cleaned up and made more stable
Fixed
- MySQL connections being closed after long idle periods
- Tab completion issues with offline players
- JOML/Vector3f export issues
- Paper/Bukkit gamerule compatibility issues
- Vanilla command execution issues caused by custom silent command senders
- Several smaller Locator Bar and marker-related issues
Notes
The Locator Bar feature is optional and should only be enabled on supported Minecraft/Paper versions.
For grave waypoint privacy, strictVisibility is available. Since vanilla waypoints do not support true per-player visibility, the plugin has to limit visibility through the global waypoint transmit range. With very high ranges such as 10000, the privacy logic may intentionally hide grave waypoints to prevent other players from seeing them.
Recommended setting for private grave waypoints:
locatorBar:
graves:
strictVisibility: true
transmitRange: 256
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:noXbBINp:KR5qtREr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:noXbBINp:KR5qtREr"
}

