Tags
Creators
Details
1.21.1-1.6.0
Compatibility
Changes
NeoSync 1.6.0
Radiation from Mekanism now belongs to the body instead of following you around. Sync into a fresh shell and you wake up clean. The body you leave behind in a shell storage keeps whatever dose it picked up, so syncing back into it gives you the radiation back rather than letting you wash it off by body hopping. Shells that come out of the constructor and bodies you respawn into from an anchor both start clean.
This only applies when Mekanism is installed. Nothing changes without it.
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:s3Vsptz0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QJvmrm6D:s3Vsptz0"
}

