MagicTorches
Wireless Redstone Torches
MagicTorches gives you a way to make wireless redstone torch connections. Each MagicTorch array has one transmitter and any number of receivers. When the transmitter changes its state (to on or off), that change is transmitted to all of the receiver torches.
Receiver Torch Types
Type | Description |
---|---|
Direct | matches the transmitter at all times |
Inverse | opposite of the transmitter at all times |
Toggle | changes state, and ignores all other transmits for a period of time. Can be used to make a torch that changes state when a button is pushed down, but doesn't change back when the button is released. |
Timer | changes state, waits some period of time (ignoring all other transmitted signals), then changes back. |
Delay | waits a period of time before processing the signal. It acts as if there are any number of repeaters between the transmitter and receiver. |
Tutorial Video
This is from the last version, but it shows you quickly how to set things up. Commands have changed slightly, and there are more options now.
German Tutorial (thanks Rogge88):
Commands
/mt create <name> [direct|inverse|toggle|delay|timer] - Creates a MagicTorch array. Receiver torches selected will be direct (default), inverse, toggle (was called delay in last version), delay, or timer.
/mt edit <name> - Edit an existing torch array.
/mt cancel - Cancels a torch creation or edit.
/mt finish - Finishes the creation or edit of a MagicTorch array, and names it <name>.
/mt direct - Sets the next receiver torches selected to be direct receivers.
/mt inverse - Sets the next receiver torches selected to be inverse receivers.
/mt toggle [time] - Sets the next receiver torches selected to be toggle receivers, with the time specified. Default time is specified in config.yml.
/mt delay [time] - Sets the next receiver torches selected to be delay receivers, with the time specified. Default time is specified in config.yml.
/mt timer [time] - Sets the next receiver torches selected to be timer receivers, with the time specified. Default time is specified in config.yml.
/mt delete <name> - Delete the named torch array.
/mt list [name] [page] - paged list torch arrays that you own, or admins can specify a player's name to list their arrays.
/mt info <name> - Shows info for the named torch array.
/mt price - Shows the current price of the array you're editing or creating. Requires economy (vault).
/mt rate - Shows the rates for creating and editing torches. Requires economy (vault).
/mt enable - Admin: Reenables all loaded MT Torch arrays, after they have been disabled.
/mt disable - Admin: Disables all loaded MT Torch arrays.
/mt reload - Admin: Reloads MagicTorches from the database.
/mt prune - Removes any non-loaded MagicTorch arrays from the database.
Permissions
Permission | Description |
---|---|
magictorches.access | basic access to the command. Needed for anyone who will create/edit torches. |
magictorches.create.direct | allows a user to create an array with direct receivers. |
magictorches.create.inverse | allows a user to create an array with inverse receivers. |
magictorches.create.toggle | allows a user to create an array with toggle receivers. |
magictorches.create.delay | allows a user to create an array with delay receivers. |
magictorches.create.timer | allows a user to create an array with timer receivers. |
magictorches.admin | allows a user to see, edit, list and delete all MagicTorch arrays. Also allows user to reload the MT db. |
magictorches.* | Gives all permissions |
magictorches.use | Gives all permissions, except for magictorches.admin |
Default config.yml
The default config.yml can be found here.
Basic Instructions
To begin the creation a MagicTorch array (i.e., a wireless transmitter torch connected to a variety of receiver torches), simply type /mt create <name>. Left clicking on a redstone torch will designate that torch as a wireless transmitter. Right clicking on a redstone torch will add/remove it from the receiver array.
Each receiver torch is assigned a type: direct, inverse, toggle, timer or delay. You can specify the type when you create the torches by typing /mt create [direct|inverse|toggle|delay|timer], or by typing /mt direct, /mt inverse, /mt toggle [time], /mt timer [time], or /mt delay [time] while creating the MagicTorch array. You can have multiple receivers of different types. Types only apply to those receivers selected after you specify the type.
When you've selected all of your torches, type /mt finish to finish creating the array, or /mt cancel to cancel the array creation. It is now active and the transmitter torch will transmit any power changes it receives to every receiver torch in its array.
Editing is similar. To edit, type /mt edit <name>. When reassigning torch types, you must first remove the receiver from the array, and then add it back again with the new type/settings. E.g., to change a direct receiver to an inverse, you would right click to remove the torch from the array, then type /mt inverse, then right click to add the torch back in to the array.
Discussion
Please see the forum for discussion on this plugin.
@sorklin
Thank you for sharing your dev build =) If someone try it : you need to restart your server after the first launch of the plugin
Bug : This : become this after make the "link"
I hope this will help you.
Thx for this :
'\o/'
.. sorry for my bad eng
Dev build here: https://github.com/sorklin/MagicTorches/downloads
It works, but there are extra debugging messages, missing or incorrect messages, missing help, missing torch list, etc. These will be implemented this week. But if you want to test it in its new form, here's the rough dev build.
Notes:
Can't wait for the update.
I am so addicted with this plugin! omg!
You done such a amazing creation. I hope that may works on 1.2.3
I'm almost done debugging. The update is 1.0 and works great with R6 (and hopefully 1.2).
Hoping for an update soon!
Your plugins are very useful and well coded. Nice job!
@sorklin
This is an awesome plugin :) Can't wait !
I'll add the activate and deactivate commands in the rewrite i'm in the middle of. They make a lot of sense.
I've added new torch receiver types:
If you check out the 'Rewrite' branch at github, you can follow along with my progress.
Would you add a command like?:
/mt activate <name>
/mt deactivate <name>
This would activate or deactivate the transmitter
I don't know what you would name this maybe something like this:
/mt click <name> /mt bump <name> but this would simulate a button press :)
This plugin is already amazing but this would make it even better because then i could activate wireless redstone from a script :)
I am excited for timer torches, I would love a plugin based workaround to having to hide enormous strings of repeaters.
love this plugin :)
i love this plugin it saved soo much time & work
i support your plugion :)
Okay, just to be clear, the delay torch waits a certain amount of time (1.5 seconds) after receiving a signal, before it will react to another change.
This was done to allow buttons to act as a switch for the receiver torch, since a button powers a torch, waits a second and then unpowers it. For direct and inverse torches, pushing a button makes them switch states twice (once for on, once for back off).
When attaching other things to a delay torch, it will react to any power change, as long as a second and a half goes by. Each time it changes power, it ignores any other changes until the time is up.
So when you say that they don't toggle, is the transmitter sending another power change after the 1.5 second period?
@sorklin
yup.
I don't specifically check if a chunk is loaded. I'm in the middle of a rewrite, and I'll add chunkloading (and detection) to the list. Chunk loading would have to be something that was optional, since it could really lag a server if the torches were done improperly.
how long of a distance can this go?
i have a minecart calling system which would be a lot easier to make if i din't have to string redstone 200 blocks. but it doesn't work (it works short distance). there were no error messages. please help.
I'll take a look, but earlier tests were good.
Just to be clear, you type /mt create delay, hit a couple of torches then /mt finish <name>, right?
@sorklin
Hm. It might just be me, but the delay torches don't seem to toggle. They change, but then they change back, just like direct torches...
Uploaded version for 1.0.1-r1.