Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 years ago
Updated last month
All versions
1.12.2-1.1.4
Release
WirelessRedstone-1.12.2-1.1.44 years ago 208
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Changes
Version 1.12.2-1.1.4:
- FIX: receivers/transmitters before mod version 1.12.2-1.1.3 breaking when using mod version >= 1.12.2-1.1.3
Version 1.12.2-1.1.3:
WARNING: This version will break working transmitters/receivers from earlier versions of this mod
- FIX: Frequencies getting corrupted and receivers/transmitters not updating anymore
Version 1.12.2-1.1.2:
- FIXED: Gui closable with inventory key
Version 1.12.2-1.1.1:
- FIXED: NBT data used correctly when placing nbt stored receiver/transmitter in world
- FIXED: (Project Red interaction) Red alloy wire can now be placed on the side of receiver/transmitter
Version 1.12.2-1.1.0:
- ADDED: Frequency Sniffer
- ADDED: Config option to color the frequency that is displayed on transmitters/receivers
- ADDED: Command to clear a frequency from active transmitters (Only use this if the frequency is "stuck")
- ADDED: Wireless Redstone blocks can now be mined faster with a pickaxe
- ADDED: Cooldown for the remote item (0.5s)
- CHANGED: Circuit recipe output from 4 to 2
- FIXED: Potential crashes caused by Remote::onUpdate and BlockFrequency::setPoweredState
- FIXED: Actual values for the frequency between 0 and 65536
Version 1.12.2-1.0.0:
- FIXED: Active frequency stays active after transmitter exploded
Version 1.12.2-0.0.1b:
- Initial 1.12.2 version
- RENAMED: Wireless Transmitter -> Redstone Transmitter
- RENAMED: Wireless Receiver -> Redstone Receiver
- RENAMED: Wireless Remote -> Remote
- RENAMED: Wireless Circuit -> Circuit
- RENAMED: Frequency Copier -> Frequency Tool
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:gdrPJIMc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2mBYHHZ5:gdrPJIMc"
}

