CreeperHeal
CreeperHeal
CREEPERHEAL HAS MOVED TO SPIGOT
Protects your server against Creepers, TNT, and griefers!
CreeperHeal is more than a griefing protection plugin : it repairs the damage done by explosions (Creepers, TNT, etc...) and fire, in a natural way! Stay a while after a Creeper made a hole, and you will see the terrain pop back slowly, block per block, exactly as it was before the explosion! That way, your players will still be afraid of Creepers, but your server will continue looking nice!
- Anti-Griefing features
- Natural healing of the terrain after an explosion
- Fully customisable
- Easy installation and configuration
- Now compatible with WG
@eccentricnz
Could you rather send me the code, please? And maybe explain what you changes, so I can see what is needed and maybe create a compatible version. Just to lention, as far as I know, Java code is implemented the same way on every platform, so there is no compatibility problem with mac/Windows/linux, but only with java 1.6/1.7
Hi, I built a version that is compatible with a standard Java 1.6 install on Mac OS, you can get it here: https:dl.dropbox.com/u/53758864/CreeperHeal-5.1.1c.jar
@nitnelave
That's a prefect way to deal with it, thank you!
@ElGipsy
Blocks are replaced when the plugin is de-activated. It basically performs a "/ch heal" when shurting down. There is no data loss, but you could say the process isn't smooth when just reloading plugins.
If the regeneration time is long, and the server restarts after an explosion happened, but before it is regenerated, what happens?
Edit: I checked the source, but couldn't find anything about saving to disk, and I guess bukkit Tasks aren't saved either. Could you confirm?
I always loved this mod. Thanks for updating! :D
I love you and would love to be a tester.
Nice to see you back in action nitnelave! Awesome Plugin! ;)
5.1 and 5.01 have a couple of problems with the newest craftbukkit build...
prevent-block-fall, prevent-fire-spread both do NOT work. I have tested it it on two different servers with the same result. I would be nice if you could fix these issues a soon as possible :)
EDIT: I misunderstood what was meant with prevent-block-fall... I thought it meant the sand, gravel wouldn't fall down when regenerated (which btw would make sense, since the terrain changes if it doesn't work like this) please make this an option in the config or integrate it into prevent-block-fall
5.1 Doe not work for me with the latest craftbukkit, I went back to the previous version and it works as it should
This file 5.1 is huge had a look inside and it contains a whole slew of older versions in the folder :Old Versions" inside the jar looks like you packed to much into it :)
New version out! Needs testing (labeled as beta for now), first on a local server then on a production one with heavy load to see if it improves performance. Please report, as I cannot test right now. (By the way, if anyone wants to become part of the project as tester, contact me). Don't forget to back up! NB : I forgot to change the version number, it still reads 5.0.1 in the plugin, but it is a new version.
i think i found my issue. i been running 4.13 since it came out. and it just stopped working in 1.3.2 R1.0 LOL
@nitnelave
Yes, but not only destroying blocks, it is necessary that they drop like a normal TnT explosion. I try to use other plugins to disable chain reaction but they stop this plugin and have no drop after explosion, if you finde how to prevent chain reaction with droping blocks this will be great.
After some testing, everything seems to be alright with the latest build. Those who have problems, can you tell me what problems exactly they are, and maybe submit a ticket? If I don't know the problems, I can't solve them.
@Jokaru
What do you mean? Do you want to prevent TNT from exploding other TNT, but still destroying the other blocks? I'll see what I can do. Maybe with the whitelist option, I'll see.
Can you add options to disable chain reaction without disabling blocks drop ?
work fine on craftbukkit-1.3.2-R1.0
@nitnelave
I cry with happiness!!!!!
Well, thanks for the help! Glad to know it was a nerfed feature instead of me just being stupid.
But no, I'm not gonna put in 150 blocks in the restrict list. I'll just wait patiently for the whitelist.
Really glad this plugin will continue! Great job, nitnelave! Don't forget the whitelist!
Also...change in my life + more free time=?????
Sorry, none of my business. Just hope everything's fine :)
Hello, everybody. I recently had a change in my life, that has given me more free time, so I will update this plugin soon.
@mindstormguy1
I know it is a bit tedious, and I may re-implement the whitelist in the next update, but for now, you can put the list of every other block in the restrict-list. So that's basically 150 blocks in there...
Sorry to spam the comments, but 2 seconds after I posted last I saw the README. That clarified things alot.
So I tried everything I did before only with 'whitelist' after the use-restrict-list: parameter.
I thought that would solve all my problems, but AGAIN nothing more happened than regenerating all the blocks EXCEPT the ones I wanted to regen.
I've tried enough on my own to get it to work. 2 hours, in fact. Could I please have a little help?
SEE POST BELOW FOR WHAT I'M TRYING TO ACCOMPLISH