Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 years ago
Updated 3 weeks ago
All versions
1.3.0+1.20.1-forge
Release
[Forge 1.20.1] 1.3.0 Wireless Redstone3 weeks ago 884
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
1.3.0+1.20.1 - 2026-10-03
Added
- Attachment block version of Redstone Transmitter/Receiver and P2P Redstone Transmitter/Receiver
- Configurable Attachment Mode: Define if the attachment block shall receive/output redstone only from/to the attached block or also all adjacent ones (except the opposite of the attached side)
- Target is shown underneath the crosshair when a P2P block is looked at with a Linker
- Frequency items show a message after a frequency has been copied or set
Changed
- Receivers are now updated immediately after a transmitter is (un)powered (before: 1 redstone tick delay)
- This also allows to send 1 game ticks to receivers (e.g. with an observer)
- Use int array tag (NBT) for storing block positions (transmitters, p2p link, ...)
- This change is only backwards compatible (i.e., you can upgrade to newer versions but going back to older one will break the redstone network)
- Improved names and descriptions in config screen
- Redstone transmitters and receivers now also update directly after block placement (also with
/setblockand/fillcommand)- If you place a transmitter with a frequency (e.g., picked up in creative with CTRL, it also shows the frequency in the tooltip), it will now correctly register itself in the redstone ether network, before it did not do that
- If you place a receiver with a frequency it will turn on if any transmitters on the frequency are on
- Note: Frequency receivers (transmitters not) now also work when relocated with frames from project-red
Fixed
- Sniffer stack size is supposed to be 1
- Sniffer and target highlight render wobbling when far out in the world due to floating point number precision (the farther out, the bigger the wobble)
- P2P transmitter and receiver block entities not updating data correctly
- Fabric:
- Wrong mixin configuration (was only registered on the client, oops)
- Redstone wire not connecting to transmitters and receivers (if played on server)
- Frequency activated with remote stayed on if:
- Switching to another item in hotbar
- Dropped by player (if played on server)
- Normal usage (releasing right mouse button, if played on server)
Optional dependencies
Any compatible version
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:2mBYHHZ5:DPmNCn5n"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2mBYHHZ5:DPmNCn5n"
}

