TeslaCoil
TeslaCoil - Tesla Coil mob control:
Version: v2.6.5
Usage: the player must construct a tower of no less than 3 iron(configurable) blocks, and connect this directly to a redstone current. While the current is active, targetted mobs and players within a configurable radius, above or below ground, will be fried. The towers ping every second by default, so mobs chasing you will quickly regret it :p Feedback/constructive criticism is welcome.
Features:
- Tower of 3> configurable blocks will continually zap mobs in a proportionate radius
- Lightning striking mobs on sand turns the sand into glass
- Configuration for radius, vertical radius, sand-to-glass, toggleable targets, and ping time
- Sign-based mob filtering, and player targeting.
- Option to hit all mobs but those specified.
- To avoid being hit as a targeted player, pumpkin helmets have been added as a safe item.
- Command /teslareload allows ops to reload config without reloading all plugins.
- Only users with the permission 'teslacoil.use' can activate coils, and 'teslacoil.reload' for the config.
- Users can be limited with 'teslacoil.limit.#' as well as 'teslacoil.use.mobs' and 'teslacoil.use.players'. shoutout to Chaznuts thanks buddy!
- Towers may have a general cap set, or be limited per group/user.
- Can warn users if they are approaching dangerously close to a coil.
- The towers can be built to shoot fireballs, wither skulls, or simply ignite targets.
- Towers can construct an iron-fence shell.
Configuration:
Permission:
teslacoil.use | Activate coils teslacoil.use.mobs | Ability to target mobs teslacoil.use.players | Ability to target players teslacoil.reload | Use /teslarelaod teslacoil.nolimit | Bypass coil restriction teslacoil.limit.# | # is the number of coils that should be restricted per user/group
Configuration Properties
coillimit: 3 #How many coils users without teslacoil.nolimit can activate, max sandtoglass: true #If false, sand will not turn into glass if a mob is standing on it vradius: 2 #Sets veritcal radius to scan for mobs setping: 1 #Sets seconds the towers wait to ping the area around them blocktype: 42 #Type of block for tower teslaradius: 8 #Can be 0(based on tower height) or a number to set a constant radius. deathblocktype: 49 #Type of block that should be present at the top of the tower for wither mode. radiusmultiplier: 1 #Used only if teslaradius is 0; for each block, the radius is this much bigger. safelightning: false #Safe lightning will only hit the target and not cause splash-damage. fireblocktype: 89 #Type of block that should be present at the top of the tower for fireball mode. buildcage: false #When a normal (not fire-type) coil is enabled, constructs an iron-fence cage around it. warnthreshold: 10 #Can be 0(deactivated) or a number to designate, from the coil's usual effect radius, at what point an approaching player is warned. igniteblocktype: 20 #Type of block that should be present at the top of the tower for ignite mode. damage: 0 #Can be 0(no additional damage) or a number indicating how much additional damage will be applied to targets.
Signs:
Signs may be placed anywhere on the coil, above the block the power is running in through.
To Filter Players:
Same idea as below, place a sign on any side of the block above where the power is input, with the first line being [players] and the subsequent lines containing a player name per line. You can have as many of these signs as there are places on the coil to put them.
To Filter Mobs:
Place a sign above the block where the power is input (doesn't matter which direction it faces), where the first line is [mobs] and the second line contains a list of all mobs that should be targeted by the coil. Alternatively, by including 'ex' on the top of any sign (like [players]ex) will put the coil in Exclusion mode, avoided the specified mobs and hitting all others. The characters are as follows:
c - Creeper s - Spider k - Skeleton z - Zombie h - Chicken o - Cow e - Sheep w - Angry wolf p - Cave Spider b - Blaze m - Magma Cube v - Villager d - Ender Dragon i - Pig Zombie n - Enderman q - Ocelot r - Wither t - Witch l - Slime
Hi! Would you be able to release the .java? Thanks!
@YotsugiOnonoki
Hey buddy!
I've actually worked to make this compatible with Spigot, once I learned of the downfall of Bukkit which honestly shocked the hell out of me. I've wondered if I should continue uploading here or on Spigot but I will update this posting with a working version with bugfixes. I appreciate your continued interest!
update pls.
Breaks the server when activated
Spigot 1.8
An update to this would be very appreciated! :D
1.7.2/ 1.7.4 Please!
@alien1947in
They are not supported yet. I'm not a dev yet, so I'm unable to update. Just cross your fingers for Darklusst! He has a life and sometimes strays away from the Minecraft scene for a few months. Just be patient, my friend!
@alien1947in
Feature request
Hook with factions so players can make coils only in claimed land.
are you guys planning to update/upgrade/modify/improvise this plugin in future?
@Chaznuts
What are codes for Horse Donkey etc.
can you add irongolem in the mob list? Thanks
@alien1947in
Probably needs an update then. What do you have on the 2nd line? Your sign should look something like this:
line 1) [mobs]
line 2) cskzwpbmdinrtl (or whatever mobs you specify on this line)
line 3)
line 4)
@Chaznuts
[mobs] k
its like that still its targeting horses.
@alien1947in
How are your signs set up? If you use [mobs] on the top, it should only attack the mobs you specify on the 2nd line.
Tesla coil is right now hard core enemy to Horses. If you are planning to place horses near ur base, Tesla coil not advised there or place horses out of range of tesla coils.
How is vradius defined? Is a vradius of 2 an additional strike radius based on the entire height? or just the base or what?
Have you observed any max numbers for horizontal/vertical radius? or is it really just limited based on how annoying you might find constant lightning or how much the server can handle?
This is functioning perfectly on 1.6.2
teslaradius: 0
radiusmultiplier: 2
However, I don't think this is working for lightning/death/fire(explosion) - it does seem to work with ignite:
damage: 20 * This should be a one shot kill for a zombie, but it's still taking about 4 hits.
The wither-effect isn't being applied to mobs, but if I get caught in the crossfire, it will get me. Any idea why?
I've double-checked WorldGuard and see:
block-wither-explosions: false
block-wither-block-damage: true
block-wither-skull-explosions: false
block-wither-skull-block-damage: true
Fire/explosion works great... but if they spawn too close to the tower, the tower will destroy itself.
Also worth noting, this works with the CreeperHeal plugin, so damage done to blocks is automatically repaired.
@CommodoreAlpha
I suppose if this plugin is causing lightning storms in hundreds of places at the same time, this could be a problem, but overall, this plugin shouldn't be causing lag. TeslaCoils should only trigger while players or mobs are nearby, which mobs are only around if players are around.
Do you have a highly populated server? Or maybe way too tall of coils? Or just an extremely low CPU limit? I believe it's either one of those reasons, a bug (which would probably print a console error), or NoLagg is lying to you.
@Lotus1000
Well, "[players]" should target any player, and you could use "[players]ex" followed by the players to not be targeted on the next 3 lines.
As for hand adding people who have a name longer than 15 characters, I'm not sure this plugin supports it at the moment. I suppose Darklusst could add something like a "[cont]<remaining player name>" to include longer names, but that's up to him. As for now, I hope that first part helps.
I've noticed that every ten minutes on my server, my CPU would spike like hell. I had NoLagg examine one CPU spike, and it pointed to this plugin. Apparently, it recorded about 2300ms for only this plugin, which is well over what I expected. I checked to see what event was causing it, and there was something mentioned about Metrics. I've actually contacted a developer of a completely separate plugin (SimpleAutoAnnounce) about a similar issue, concerning a lag spike having to do with Metrics. He hasn't responded yet, and I doubt he will.
I'm not trying to point any fingers at this particular plugin, because I'm starting to think the lag occurs when plugins call Metrics, or something along those lines. I'm just wondering what your take on this might be. Normally, I'd ask somewhere else about this first, but NoLagg's lag examination pointed only at this plugin during that lag examination, which is strange.
EDIT: I did two more lag examinations, and both still pointed at this plugin, under the same event.
Is there a way to have the coils target players with names longer than one line on the sign? I have players who cannot target others because the other playername does not fit on a single line. I've tried putting it on two lines, and other variations, but no luck. Suggestions?