Wireless Redstone
Instant redstone signal transmitter, get rid of those wires!
Help translate WirelessRedstone in your language!
This plugin is used worldwide. For that reason, I made it possible switch easily between languages directly in the configuration of the plugin (see "How to use"). If your language is not available, you can translate it on this website and I will add your own work to the next release of WR!
Demonstration Videos
Upcoming features. ( Or planned )
- Please note that we're doing our best to make WirelessRedstone bugfree, it still may contain a few bugs and such.
Links
- Metrics
Thanks
- Thanks a lot to Wmisiedjan, the creator of the plugin. He left the project more than a year ago, and since that moment, I'm the developer of the plugin. I made big changes, but some of his code still is in the plugin. He was also a great guy because the code was open, that's why I could take it and modify it. Thank you, mate ;)
- Thank you a lot to bb-generation who optimized the configuration part and update the plugin to maven.
- Thanks to my beta-testers (cannonb4ll, s32ialx, and Kervinou), your help is great!
- Thanks to all the persons who help me to improve this plugin, and report bugs.
Donate
Pssst... Do you like my plugin? Then please donate a bit to encourage me!
Have an issue?
Please report it here
If you want to post it here, please post:
- a description of what's happening.
- The version number of WirelessRedstone, and Craftbukkit.
- An error log if you could get it.
Suggestions
If you want to submit an idea, please post it on this page with the label suggestion.
Looks like it doesnt matter how the Receiver of Channel "test1" is connected to the Transmitter of Channel "test2"... The bug appears with normal redstone too
There seems to be smth. strange with the mechanic that denies the removal of blocks that are connected to a WR receiver/transmitter too It denies the removal of blocks that are near a receiver/transmitter but are not connected to it
Hi again... Think I found a nasty bug in the current Version (2.5)
Scenario:
Expected behaviour:
Current behaviour:
The servers console does not show any stacktrace
@Lihweja
Hi Ligweja,
This issue isn't because the new switch and clocks. I changed the gate logic into OR gate (click here for more info). This causes the behaviour you have seen with the piston. It was requested by someone on personally I think it will make much more sense. I maybe make a poll for which gate people prefer or a config option to change it or stick with this, I don't know yet.
Regards, Bart
Hi Bart... I love your plugin and use it very often in my world. Not having to build insanely large redstone-wires is a very nice feature. What I don't want to use are the new receiver-types (switch, inverter, clock, ...) cause I feel the need to create these mechanics myself.
When I updated my server to 1.8 (from 1.7) and the WirelessRedstone-Plugin to 2.5 I notived a (imho major) change in its behaviour of the default transmitter-receiver pairs.
Scenario: This is my default scenario for the many secret entrys in my castle where two or more levers are opening/closing one entry.
Old behaviour:
New behaviour:
I know there is the possibility to just replace the levers with buttons and use the switch-receiver. But as I already mentioned, I don't want to use the advanced-technics you provide. Is it possible to provide a receiver in one of the following versions that behaves like it did in the old Versions?
In appreciation of your work, Lihweja
Hello, I can toggle the Wireless redstone reciever on with a redstone input (lever, button, etc) but upon retoggling the Lever or button the reciever stays in the on position.
I can toggle the reciever off by right click the Transmitter sign. If I try and toggle the transmittor via right click the reciever turns on then off as if using a button.
Thank you!-Aritex
@foxi69
In the config, located /plugins/WirelessRedstone/config.yml
Change the variable: "Language:"
You need the put in your country abbreviation, eg. nl. If the language is not working after a reload then the plugin doesn't have your language (yet).
@Bart0110
how I can select my lang then?:D
I love this plugin!
But is there a possibility to make a delay receiver that only will delay when you turn the redstone on and a type that only will delay when you turn off the redstone?
Like this:
- Transmitter+lever > Receiver with a delayon of 10 sec > redstone system
- Transmitter+lever > Receiver with a delayoff of 5 sec > redstone system
A sign format can be: [wrr] (channelname) [delayon] (delay in ms) and [wrr] (channelname) [delayoff] (delay in ms)
@X_angelz_X
I'll add this as a feature. For the time being you can use /rg flag <region> disabled-cmds wr,wirelessredstone
@Bart0110
Well, i've given my VIPs the following permissions:
- Wirelessredstone.create.*
- Wirelessredstone.remove.*
- wirelessredstone.commands.lock
- wirelessredstone.commands.list
- wirelessredstone.commands.info
- wirelessredstone.commands.help
Though when they do /wrt TESTSIGN the sign gets placed inside the region they are in even if they don't have perms to place inside this region.
@X_angelz_X
Do you mean that you can use commands when it's disabled in a WorldGuard region? It's weird because we don't use a very advanced system
The commands are bypassing WG regions :/
Thank you!
We use Bukkit 1.7.9-R0.2
@Xolgrimm
Which MC version are you using?
I have found a Bug!
If you control the transmitter with a Redstone cable it works as long as the cable is not longer than 3. If it's longer than 3 and you deaktivate the transmitter it will give a very, very short signal to the receiver This one can determine if one sets a Command Block directly to the receiver.
Test setup: TrrrrL RC
T = transmitter sign, R = receiver sign, r = redstonewire , L = Lever, C = Command Block [tell @p test]
@CloudeLecaw
I don't fully understand the problem. I reconstructed your setup and both levers worked.
@X_angelz_X
I'm working on the Switch. Idk if I add every single gate. Also the signs are OR gates.
@foxi69
Thank you! Your translation will be added in the next update.
@CloudeLecaw
Well obviously we can do all of that, but I only suggest it because this plugin is aiming at what most don't think, a simplified and easy to use redstone system, that isn't redstone. Nevertheless it doesn't have to be added, just a suggestion that a lot of my players have commented on. They are excited to see switch receivers.
Can't wait for the Switch, possibly add in an OR system as well?
That would be pretty epic. Currently using this a VIP perk on
our server.
I translated the Hungarian lang and edited the bad grammar in the file!
(I'm rErEaT on crowdin.com, I hope you will approve my translate and add to your official plugin!)