Links
Tags
Creators
Details
1.2.0
Compatibility
Required content
Changes
A full audit, seven bug fixes, and a feature pass grounded in what players ask for from spawn-proofing mods.
New features:
- Suppression feedback: an action-bar ping (or particle puff) when the conduit eats a spawn. suppression_feedback: off, actionbar (default), particle.
- /mobconduit visualize: draws each conduit's coverage volume in particles for 10 seconds.
- radius_shape: sphere (default) or cylinder (same horizontal radius, full height).
- Status hologram: floating "Mob Conduit / radius N" text above the crystal — a vanilla text_display, nothing registered. hologram: false disables it.
- disabled_dimensions: dimension ids where conduits do nothing.
- suppress_exempt_types: mobs the conduit leaves entirely alone.
Behavior changes:
- Neutral mobs are no longer suppressed: endermen and zombified piglins spawn and persist inside the radius; spiders and piglins stay suppressed.
- Long-range effects (aura, beam, visualize) are sent with the server's overrideLimiter flag, so they render past 32 blocks.
Bug fixes:
- frame_block changes now fully tear down invalidated conduits (obsidian restored, rebuilds re-arm).
- frame_block: minecraft:air is rejected instead of activating every crystal for free.
- Erasure lights no longer strand on chunk unload; light placement can no longer sync-load a chunk.
- Teleported crystals deactivate the conduit they leave behind; reload drops crystal-less conduits.
- Fixed a per-tick drain that stayed hot after the last conduit deactivated, a visualizer leak across world restarts, and a sidebar leak across integrated-server worlds.
Server-side only; vanilla clients need nothing. Minecraft 26.2, Fabric Loader 0.19.3+, Fabric API 0.156.0+26.2, Java 25.
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:tBSSIv55:d38MtTje"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tBSSIv55:d38MtTje"
}

