Links
Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 6 months ago
All versions
1.3.0+1.21.1
Release
Graveyards & Ghosts (Graveyard Respawn Points) 1.3.0+1.21.1last year 379
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
This update resolves stuttering issues and improves existing features.
This update adds a new option that will affect users disabling player ghosts on death.
Added
- Added
enableGraveyardRespawnPointsoption. This option is set to true by default. This option allows players to allow respawns at graveyards without the Ghost Effect. The Ghost Effect will only be applied if bothenableGraveyardRespawnPointsandenablePlayerGhostOnDeathare set to true. If you hadenablePlayerGhostOnDeathset to false, you will want to setenableGraveyardRespawnPointsto false for the same configuration. - Added
enablePlayerGhostParticlesoption. This option is set to true by default.
Changed
- Changed supported Platform version to 1.3.0. This resolves stuttering issues and includes new features.
- Changed mixin filenames to avoid collisions.
- Changed usage of
TickTimertoServerTickTimer. This helps resolve stuttering issues. - Changed most blocks to act like their respective material types. Resurrection statues are now only blast resistant if made from Obsidian, Crying Obsidian, or Netherite. The tombstones for these same block types no longer instant break to represent their hardness.
Fixed
- Fixed breaking times of Resurrection Statues. Resurrection statues were copying Netherite Block properties and had an extremely long breaking time.
- Fixed location of language files.
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:bhTQJIiQ:pCMyX329"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bhTQJIiQ:pCMyX329"
}

