Tags
Creators
Details
26.1.2-1.4.3
Compatibility
Changes
NeoSync 1.4.3
Picking a shell away from a shell storage no longer looks like an ordinary death. The death screen stays out of the way, nothing is announced in chat, and you are carried straight into the shell you picked instead of being asked to respawn first. Your body still drops what it was carrying where it fell, so grave mods keep working exactly as before.
Choosing a shell while you are already dead now takes you there right away as well, rather than waiting for you to click respawn.
If a sync cannot finish, because the shell was broken or the storage is gone, you are put back where you were with the death screen returned to you, so there is always a way out.
Faulty pack scripts listening for sync events can no longer disconnect players. Errors are written to the server log instead.
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:yPXQQiW4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QJvmrm6D:yPXQQiW4"
}

