[MECH] MagicTorches v1.0 - Create Wireless Redstone Torches [BUKKIT DEV]

Looks amazing. I might end up using this on my server.

Just an fyi, I'm in the middle of a ground up rewrite that will enable torch array editing, new torches, etc. Sorry for the delays.

dam guess i gotta wait for the 1.1 version

As I mention on bukkitdev, the new version will have two new torch types, torch editing, enable/disable per array, etc.

The old version will work on 1.1, at least in my testing.

Hi!First of all, thank you for this plugin, good idea, well made and easy to use. Exactly what I was searching. Installed it, used it, works just fine. But on server restart I get this nice NPE:

And so on, for every arrays I created. In game, there's no array then, of course, they failed at loading...

I'm using latest recommended bukkit, I guess it might come from that?

Nope. Most likely its from a multiworld plugin that hasn't loaded. Are you using multiverse or some other multi world plugin?

Yup, affirmative. I'm using "My worlds"

http://forums.bukkit.org/threads/ad...3-multi-world-plugin-with-a-touch-1795.31718/

Alright, say we want hidden redstone with this it is easy to do. But if it is on top of a Building at night there will be an unwanted glow. Could you add like a .cfg or something to edit the block id from Redstone Torch? If not i will deal with it.

@Psychokiller1888, I'll try to implement something for that. I'm in the middle of a huge rewrite, so it may be a little while.

Yeah no problem, i can wait. Thank you!

I've been getting this error in my log with Magic Torches. What's going on? I'm using bukkit-1.1-R3-b1846jnks

You need to paste your whole log (from startup to the errors) in pastebin and link here. I can't work with screenshots of logs.

Does this work? I lost the very top of the log because a couple players logged in and the log scrolled down beyond the absolute start. Most of it is here, though.

http://pastebin.com/BZGKx5w1

No. In order to help you, I have to see the entire log, from boot to where the problem begins.

Thanks, It's brilliant! Just what I needed and it's really easy to use.

I haven't had any further issues with this plugin since that original one. It's been working perfectly as intended.

In your demo video you mention that you can setup multiple transmitters for the same array. How do you actually do this? It seems to be overwriting the 1st transmitter with the 2nd (it's only keeping the last one)

I meant setting up multiple arrays (with one transmitter each) for the same receiver torch. That is, a receiver can be in multiple arrays. However, this may make it act erratically.

By the way, I just finished initial coding of 1.0. I have some extensive testing and debugging before it will be posted, but this means R5 compatability and:

• Two new torch types (with new ones being simple to add later) -- timer and delay (current delay torch renamed to toggle).
  • Timer torches receive a signal, click on (or off), waits a period of time, then click back to original state.
  • Delay torches receive a signal, wait a specific period of time, then change state. (Acts as if there is a repeater between the transmitter and receiver).
• Vault support (for economy). Torch arrays are priced by whole array (creation and editing), and/or per receiver type (or you can keep em free!)
• More granular permissions for specific receivers (i.e., you can make it so that people can only create direct receiver arrays, etc.)
• Full torch editing -- allows you to edit an array, just like when you created it (i.e., add/remove receivers, change transmitters, etc.). Arrays are inactive during editing process.
• Better torch information tools (e.g., receivers know who their parents are).
• Transmission Signals are now handled through events, so its possible to hook them with other plugins
• Transmission can load chunks, if they need to, and you allow it
• Arrays can be distance limited
• Admins can activate/deactivate all of the arrays on the fly (doesn't yet do specific array activation/deactivation).

This may take a bit of time to fully test, but the coding is mostly done.

This is almost finished with debugging, and it fully works with R6 (and hopefully 1.2 when it goes RB).

Code:

[GRAVE] Could not load 'plugins\MagicTorches.jar' in folder 'plugins'
org.bukkit.plugin.InvalidPluginException: java.lang.NoClassDefFoundError: org/bukkit/event/player/PlayerListener
        at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:148)
        at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:287)
        at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:211)
[...]

At the server start.
build 2029

The current version will not work. However, I have a dev version of 1.0 that works well. The problem is that there are still bugs and a few missing features (paged listings and help) that need to be added before it ready for prime time.

Can we help you to find bugs ? (can you share the dev version ? )

I'll post a dev if you want, but its not quite finished (i.e. no help, no list of arrays, etc.)

Hi! How is the update going? I'm anxious to see this working in 1.2.3. I haven't upgrade my server just waiting haha.

Just posted 1.0 to Bukkitdev. It may take a bit of time for the mods to approve it.

Awesome, it works. Thank you!

i can only set one transimiter to the array :S how could i make multiple transmiters to the arrey ?

You can't. Make multiple arrays -- remember, receivers can receive from multiple transmitters.

Hey, just curious, does anyone experience lag on the server when the wireless torches are toggling between on and off state? I'm trying to create sort of a whole village lighting system, and thought it'd be kinda cool to have them all flash on and off, but every time they switch minecraft pauses for a split second? Happens to everyone on the server, not just me.

I do admit I have a fairly huge amount of receivers though. I tried disabling chunk update on receive but didn't seem to help.

Awesome plugin in any case

This plugin definitely isn't optimized for very large arrays. If there is enough need, I'd add some queuing so that it wouldn't try to do all the transmit/receives in one go.