
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.3
Compatibility
Changes
Bug fixes
- Fixed: the explosion sound is back. The predicted explosion was playing its sound through a call that does nothing on the client, and the mod was then silencing the server's sound as a "duplicate" of a sound that never played — so anchor detonations were completely silent. The boom now plays instantly on detonation.
-
- On 1.20–1.20.6 the sound stays server-timed (there's no injection point to suppress a duplicate on those versions), so it plays slightly later there instead of not at all.
-
- The sound is also no longer silenced when client-side explosion prediction is turned off.
Same coverage as before: one jar for Minecraft 1.20 → 26.2, the right hooks are picked automatically at launch.
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:oNhZvs5m"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jrlJ1e3H:oNhZvs5m"
}
