Links
Tags
Creators
Details
1.2.0
Compatibility
Changes
-
Rebranded to Actrium
-
This update will require a reset of your configuration. Resetting configuration is not automatic.
-
Please delete the ActriumGraves folder in your plugin folder to reset your config.
-
Overhauled the configuration system and improved config.
-
Added the "/grave delete" command, allowing players to remove their own grave if looking at it. (Requires "actriumgraves.delete" permission)
-
Added "/grave info" command (Only runnable by players with "actriumgraves.info" permission)
-
Added "/grave admindelete" command (Only runnable by players with "actriumgraves.admindelete" permission)
-
Added super customizable respawn items.
-
Fixed issue with MongoDB throwing errors.
-
Fixed error when using MongoDB or MySQL after deleting world.
-
Fixed bug when void dying in the end dimension.
-
Fixed grave despawn task using memory even if despawning is disabled.
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:UGgxVu6h:uQZ4hPMd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UGgxVu6h:uQZ4hPMd"
}

