v1.0.1-beta
Compatibility
Changes
A big update!
Changes
-
The data pack is now compatible from 1.19.4 to 1.20.1.
-
The mechanics of spawning a grave has now slightly been changed.
- Now if you die in the void, it will attempt to spawn the grave at y position +1, but it won't move down.
-
Graves can no longer spawn inside some blocks (such as slabs), but now can in some other blocks (such as bushes).
-
Graves can now despawn. By default, they despawn in 90 minutes.
-
Items dropped from graves now by default despawn in 45 minutes, instead of 10.
-
Players now can only open their own graves, by default.
-
The interaction box of the grave has been shrinked, making it a little bit harder to open/break the grave.
-
Graves now display their despawn timer in addition to the grave's id and the owner of the grave.

-
/trigger sgrave.grave_infowill now show the grave despawn timer.
Additions
- Added 5 new configs:
- Void invulnerable items, Robbing, Locating, Put dirt below, Grave despawn time
- The descriptions of all configs are in the game.
- Added new logo!
Fixed
- Breaking a grave with experience more than 32768 (103 levels) would give negative experience, which also broke all tools with the Mending enchantment.
- Fixed by changing the maximum experience level that can be stored from 127 to 100.
Technical
- Configs no longer use data storage and now instead use scoreboards.
- Some functions have now been rearranged.
- Tags now use
{id: "tag", required: false}instead of"tag", which fixes a few issues. - Added some new easter eggs.
Known issues
- An unnecessary python file
sort.pyhas been left out in the game's code, but this will disappear in the future. - The xp dropped from opening a grave will repair tools with the Mending enchantment.
There are more features added, changed or fixed in this update, which I can't remember.
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:slWK6iug:6YcHo48e"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:slWK6iug:6YcHo48e"
}

