Tags
Creators
Details
1.21.1-1.4.1
Compatibility
Changes
NeoSync 1.4.1
Respawn anchors can now be handed out as a single use. Add true on the end of the anchor set command and the anchor is spent the moment the player syncs into it, so it catches one death and then it is gone. Leave it off and the anchor keeps working the way it always has.
There is also a new ensure form of the command. It gives a player a single use anchor only when they have nothing left to sync into, and does nothing at all when they still have a shell standing. Pack makers can safely run it on a timer or on login to keep players from getting stranded with no way back.
The anchor list command now marks which anchors are single use, and every anchor command reports how many players or anchors it touched so scripts can check the result.
Optional dependencies
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:QJvmrm6D:IXAHHp6j"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QJvmrm6D:IXAHHp6j"
}

