Links
Tags
Creators
Details
1.2.0
Compatibility
Changes
-
Per-dimension toggle for campfires
-
Per-dimension separate toggle for soul campfires
-
Separate radius for regular and soul campfires
-
Separate
max-distanceandsoul-campfire-max-distanceoptions in config, specifying minimal distance between campfires (can be different from the radius) -
A sound for respawning on campfires
-
override-confirmation-timeoutoption can be set to 0, meaning that the player can not override existing campfires unless they are broken -
allow-delete-commandoption, when set to false, disables the/cc deletecommand, forcing players to break checkpoints manually -
require-empty-hand-or-sneakoption in config, which restores the ability to cook food on campfires with the plugin -
scan all checkpoints during
/cc listcommand and during respawn, to remove all missing / invalid / extinguished ones. -
Support for respawn anchors
- respawn anchors can be enabled to use checkpoint mechanics.
- unlike campfires, they aren't limited by distance
- respawn anchors are not affected by
min-distanceoption and can be close to campfires - there can only be one anchor per player
- anchors can work in all dimensions (configurable)
- anchors no longer override bed spawnpoints
- it is possible to re-enable vanilla anchor mechanics in the nether, while using anchor checkpoint in another dimension
In respawn priorities, anchors have the same priority as beds. A bed is overriden by an anchor if one is charged. If a checkpoint has higher priority over the bed, it would also have higher priority over the anchor.
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:PHISyXe3:HHzDe1Bj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PHISyXe3:HHzDe1Bj"
}

