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
Quick problem I have with your plugin... Why are you limited to 1 input and endless outputs? I find multiple inputs to be a must for this kind of plugin to fulfill it's duties of being an overall really good wireless system.
Example... I used a similar plugin with multiple input capability to bypass the idea of a bulky, timed, memory array.
The idea was... i wanted to write: Abusive with pistons. Each letter pulses out of a wall, but in the same location. I created a figure 8 with pistons connected to it, and simply used a redstone clock to power inputs down the track, which then connected to arrays that powered only the necessary pistons. However... In order to do that, each designated array per letter, had to use the same input (say the top left piston input) at different times without being connected.
Since you only allow 1 input, although you can stop the use of a redstone line, it's very difficult to simplify more complex things, or well, make them less cumbersome for that matter.
Please take this as a suggestion or construction criticism, not as: "This addon is better than yours... Blah blah blah". The only reason I mention this here for you, is because from what I can see, you're the only modder that has actually updated his project to 1.3.1, meaning you might actually care.
Thankssss
PS. Unless ofcourse, I am wrong, and if you create a new array with a different input, you can use the same output that you are already for another array...
Updated for 1.3.1 and fixed a few minor things (including load spam).
Will do. I only enabled for debug purposes and forgot to shut it back off. I've been super busy with getting a major update done to the game community I support. But i have a bug fix and this that i'll roll out in a few days.
for your next update how about making the startup cleaner, right now everytim I start up my server I see lines naming every single little detail of each array for MT which makes the startup log look massive how about changing it to look much much cleaner like this e.g.
wouldn't that be cleaner than this
When i'm entered this command... /mt toggle [time]
CraftBukkit-R4.1
I mean add a command line activation of the mod with the right click option?
... sorry wasnt sure if I was being clear...
-Ams
Maybe you could add the option to have us look at the torch to assign it with your mod?
Appreciate the help! -Ams
nay... it would work yes.. but your right click assigns the torch I believe, and SolarRedstoneTorches right click sets the level of when it should turn on ... so .. its one mod or the other unless someone gives up the right click .. or I have to find something else <shrug> Thats cool though, if its lag you were worried about, I dont know.. solartorches dosent seem to lag that I can tell, maybe as the world gets bigger ... we ll see...
Make a small circuit. Make the SRT's send a signal to the transmitter (that you can hide). Then it'll transmit when the SRT goes off.
I don't want to do light sensing, because its likely to be a very laggy thing to implement, and wouldn't work in the current plugin structure.
Its important to remember that Magic torches can be part of other circuits, so the transmitter can be triggered by other torches and/or redstone circuits.
Do you think you could give your torches light trigger options?
If only I could get this mod and solar redstone torches to work!!
-Ams
This seems to be working great. My players are going to love this :) Thanks for the plugin!
Is there away 2 set more than 1 transmitter?
I created a ticket for you. I'll take a look. Check the ticket for questions and whatnot in the next few days.
Houston, we have a problem.
The mod tends to (or rather replaces) DELAYED torches with TIMER torches, on server start. ( technically it keeps the 7.0 s, but I cant do anything with timer ones )
BUT the DB of yours clearly shows delayed torches. Even after /mt reload
So, one question: WTF is happening ?
DB serverlog
And also, it would be nice if I could set up delayed and inverted torches.....because torches are on by default......(managed to do it once, never again)
Thanks!
Just wanna show my support for this plugin! :3 It makes making contraptions a lot easier and without all the cluttered mess of redstone too. My friends and I enjoy using MagicTorches!
Scratch my previous comment it's working, i was just doing it wrong like an idiot
Really love the plugin, but it doesn't seem to be working for 1.2.4 yet do you have a version that works for it? or are you planning on just skipping 1.2.4 since i believe 1.2.5 is soon to come out.
Great plugin that has helped us create a ever increasing switch track network across our world (among other things).
Thanks!