AntiCreeper
AntiCreeper
- Tired of rebuilding every building in your server, because those green things ruin them all the time?
- Tired of filling in all the explosion-created holes? Wish you could tell people to do it themselves?
- And also you hate the mods which make the creepers just walk around without doing anything to the players?
- Do you have a nether paradise? Do you hate the fireball spitting ghasts or players exploding beds?
- Too much grief with TNT?
- Those missing or randomly placed blocks from endermen triggering your OCD?
- Having fun with fireballs but don't like the fire? Or want creepers to burn stuff too?
- That huge hole left by Wither boss got you down?
- AntiCreeper config.yml too confusing for you?
- Want to spawn an Enderdragon but don't like the wholesale destruction?
If You say yes to just one of the questions, then this plugin is for You!
This plugin by Filbert66, though its roots come from @Rothens.
Features
- Cancels creeper environment-destroying behavior.
- or optionally allows it but can leave 100% of destroyed blocks, allowing easy rebuilding.
- and/or configure a height below which it is allowed, or alternatively above which it is allowed.
- and/or define a list of blocks that are (the only/NOT) affected
- and optionally disable sound & smoke or player damage, if you really want to
- and selectively configure which entities receive damage or not.
- Cancels TNT, Fireballs, Wither explosions, ender crystal, unknown explosions (from other plugins) with all of same options as for creepers, above
- optional different configuration for wither skulls and TNT minecarts.
- But can damage the players in all cases! (you can now control this, too)
- Cancel various enderman behaviors, including block pickups, or just put-downs.
- with configurable white/blacklist!
- cancel damage caused by lightning (for you spell-makers out there).
- disable Wither & Ender Dragon moving through and damaging blocks
- both support configurable blocklists
- Detailed configuration now available!
- Multi-world support; [In 4.17] you can now turn off Anticreeper's behavior for certain explosions in certain worlds.
- In-game commands to query, set, and save configuration items
- allows testing config changes without making them permanent
- save configs to disk without every manually editing config.yml.
- disable exploding beds in the nether
- Override explosion power to strengthen/weaken each explosion type
- Option to throw destroyed blocks a distance based on proximity to explosion center; or, throw whole blocks and they get placed around [n 4.18].
- Supports multiple languages on all player messages
- See Languages and Translations page for details.
mobGriefing rule not the same
I hope you see that this does much more than the mobGriefing game rule. Yes, it's almost the same as the default Anticreeper config, but not the same. In fact, this plugin started because it seemed incorrect that creepers can't blow up blocks when in the deep dark, mining. See my comment on this for an equivalent Anticreeper config.
Anticreeper allows you to do more, including fine-tune what/who gets damaged from explosions, at what height/depth you need to be to cause block damage, create protected block types, allow damage from one mob explosion but not another, and lastly but perhaps most significantly, nerf TNT damage which mobGriefing does nothing about!
Configuration Description & Hints
Please READ THIS LINKED PAGE FIRST before you post here with problems.
Still Not Working for you?
Most common error is misspelling your world name. Log into your world and execute these commands in game:
ac world ac world on ac save
First tells you if you had it on in that world. Second activates it, just to make sure. Third saves it so it sticks.
Commands and Permissions
Details about in-game commands and associated permissions are found here.
Statistics
Since 4.8 the plugin now sends statistics to mcstats.org. These are completely anonymous and help me as a plugin developer know how the plugin is being used. You can view the same data by clicking below. If you want to turn it off, simply edit plugins/PluginMetrics/config.yml and change opt-out: false to true
Planned Features
Click here to have input into what I should do next.
Any donations are welcome and will inspire more features. :)
unsure of why withers are able to kill peaceful mobs.... please help
ah i just read where u say that turning off block damage will make fire unlikely to happen. dannngggg
ok so i just found out that turning off block damage in anticreeper disables fire from being able to occur. cant i have just fire and no block damage?? :p
just realized, ghast fireballs arent creating any fire like they should be. fireball block damage isnt blocked in worldguard, and fire for fireballs is turned on in anticreeper. is there anything else i should look at andor change??
well, i did.. but once i came to a temporary resolution to this problem i actually realized that id prefer not to have fire in most of my server worlds :) sometimes it doesnt go out, and i dont like that it destroys drops, and also, it could lag the server with fire being created in all worlds a lot, ive fine tuned my anticreeper and worldguard perfectly now, and the peaceful mobs are staying undamaged when set for that so that works :D
@ChillerKraft
You want fire on in ALL worlds, but block damage only in some? Hmm...
ive been using worldguard as a way to stop block damage in some worlds, but theres a big problem, i dont get my beautiful forest fires anymore from creeper explosions etc when i have block damage turned off in worldguard for that world. i wish i could block just block damage in some worlds, without losing the fire settings
i dont know if i knew this a while ago, but i just found out now , anticreeper does not protect drops in 1.7.10. i thought i had this problem figured out when i moved to 1.7.10, but im guessing i forgot that it was 1.7.9 that i found it it works on. great im so happy about this! and excited for the new features too :D
@ChillerKraft
See full reply here.
goooo bukkitdev make us proud :p
cool, ive wanted a way to stop ppl from griefing or accidentally killing passive mobs with explosions while still allowing them to use explosions on hostile mobs only :) especially and mainly for skyblocks, or home type worlds on my server involving farming and animals and lots of explosions. ty and my second request was mainly, can i control each entity damage nodes worlds seperatly or do i have to put the excluded list under all entity damage nodes,. im guessing i can do it seperately but just makin sure for example nerfentity: player: true excludedworlds world1 item excludedworlds world2
?:P sry for bein messy
@ChillerKraft
My proposed exclusion list would turn off AC behavior in listed worlds, so you'd set explodeblocks to true and list world2 in exclusion_worlds.
Today only have one tomobs setting. I could add two new settings tohostilemobs and topassivemobs.
Not clear on your second request. Can we move this discussion to Planned Features page?
if i wanted blocks to be exploded in world1 but not world2, could i set explode blocks to false and put world1 in the exclusion list?
and idk if ill wanna change this stuff in the future but could i have unknown player explosion damage set to false and put a world exclusion list under nerfplayertntdamage specifically so that its allowed in some worlds and doesnt effect other entity damage entrys? :)
and can i somehow make explosions only hurt hostile mobs and not passive??
@ChillerKraft
No. Drops affected by .entitydamage.todrops
ok ty also does setting explode blocks to true also make drops explode? im gonna do some testing soon but i hope its not that way,
@ChillerKraft
Look at your server log for which plugins are loaded first, etc. If the plugin doesn't set its event priority it is done in load order. The last plugin to get notified of an event can change what all the previous ones did.
can u help me find out how to find out what my plugins priorities are exactly?
@ChillerKraft
1. Priorities of plugins are set in their code, or if not they are EventPriority.NORMAL. If same level, depends on which loads last. I don't set the priority so if another plugin has higher priority than normal (or loads afterward) it can change the event.
2. Secondary control so that one type of explosion is modified in one world but not another? I already have nerfed_worlds, but that changes behavior for all explosions in the nerfed worlds. Sounds like you want AntiCreeper active in two worlds, but behaving differently in the two? Wouldn't be hard to add a new exception_worlds under each type of explosion node, so that you could turn off AntiCreeper's behavior for that particular explosion type in that world. Is that what you want?
3. If another plugin modifies the explosion event, it may change the behavior set by AntiCreeper and explode drops. Recommend only using one plugin to modify explosions.
quick question, can you tell me anything about priorities with this plugin and others? i noticed something nice today, i can have explode blocks on for all options, and turn them back off with worldguard for certain worlds!! :D but can i do this with other explosions? from other plugins? i dont see an option like that in worldguard, i might have to go to worldguard about that question.. another thing i wanna note quick, still gotta do more testing but, seems to me like when i started making those kinds of changes, or around that time, all explosions starting breaking all my drops again all the time even lightning! and i have it set not to in the anticreeper config and its worked fine for me recently until today :S 1. priorities 2. a secondary other explosions control so i dont have to turn ac off in a world to have it on in another 3. drops started breaking again during any explosion.. ty
@ChillerKraft
Endermen only pick up certain blocks already; they already have a built-in whitelist in vanilla MC that I don't and can't modify. So the whitelist for endermen is best used as a whitelist (setting whitelist=true), starting with the existing whitelist from vanilla:
Read also this section of Config help. It also has a link to the descriptive version of these blocks rather than the ID numbers. Hmm... I note looking at that list that the list has expanded (with the addition mainly of new flowers) since I built the ID list above.
Note that you can also use strings instead of IDs in the blocklist. Read description of that here.