Tags
Creators
Details
1.21.1-1.6.1
Compatibility
Changes
NeoSync 1.6.1
Server operators get a new command. /neosync purge <players> [dimension] removes a player's shells completely, both their own record of them and the copies held in blocks. Any body still inside a block drops its inventory and experience where it stood. Leave the dimension off to clear every shell a player owns, and once they have none left they stop counting as artificial.
Syncing out of a body that was not sitting in a Shell Storage or Shell Constructor no longer errors on the server. The sync itself went through, but the shell list stopped updating and old entries stayed in the selector until you rejoined.
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:GXmKNPrB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QJvmrm6D:GXmKNPrB"
}

