Links
Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated last month
All versions
0.1.2+mc26.1.2
Release
0.1.2+mc26.1.24 months ago 96
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Changed
- Lock and Private now actually protect a block. Only the player who placed it (or a server operator / creative-mode player) can open its config or change a transmitter's mode. Previously any player could retune or toggle any block.
- Large wireless networks are much lighter on the server: a signal change now only nudges the receivers whose output actually changes, instead of every block sharing the frequency.
- The "Paired: N receivers" / "Receiving from N" counts on the config screens now only include blocks that are actually within range.
Fixed
- Transmitters and receivers no longer go dead after being broken and re-placed (or moved by a hopper, or pick-blocked in creative) — they keep their channel and frequency.
- Receivers now behave like a redstone block: they power adjacent dust and components but no longer push a signal through a solid block, and no longer leave a stale "ghost" signal behind an adjacent block.
- A config screen left open after its block was broken can no longer create a permanent phantom signal.
- Transmitters in Fixed / Always On / Always Off mode no longer re-broadcast to the whole network when their redstone input changes without changing the output.
- On NeoForge, receivers no longer fire a redundant redstone neighbor update when their chunk loads.
- Hardened server-side handling of edit-lock, value limits, and network packets against malformed or unauthorized input.
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:htFCXw6b:f6b9eR7o"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:htFCXw6b:f6b9eR7o"
}

