
OptiPlus-Anchor
Removes the wait between triggering a charged respawn anchor and the block clearing from the world. The anchor is set to air on the client immediately on interaction, so the slot is ready for the next placement without any server-confirmation lag.
2.0.2
Compatibility
Changes
Slimmer & fully standalone
- ~3x smaller download — the jar went from ~335 KB to ~125 KB.
-
- The anchor jar is now fully standalone: it no longer bundles any end-crystal code.
-
- config/optiplus.json now only contains the section for the OptiPlus mod(s) you actually have installed.
-
- Safer config editing: deleting a setting from the file now falls back to its default instead of silently disabling the mod, and config writes are crash-safe.
-
- Same coverage as before: one jar for Minecraft 1.20 → 26.2, the right hooks are picked automatically at launch.
Known issue: the explosion sound is still missing when an anchor blows up — will be fixed in a future update.
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:jrlJ1e3H:gzDE0eiQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jrlJ1e3H:gzDE0eiQ"
}
