WaterProof
Quote from Siguza:The Future?
Since Spigot is still standing and Sponge is slowly getting somewhere, I'm not exactly sure what to do with my plugins, but I'll stick around.
I think I will port most of my plugins to Sponge, but some (like NBTLib) will hopefully not be necessary anymore.
For now, I've set all my projects to "inactive", except for VirtualPack, which I will keep compatible with Spigot, until I ported it to Sponge. If you really want to see any of my other plugins updated to Spigot, just comment on its project page.
WaterProof
[ Configuration ] [ Download ] [ Javadoc ] [ Source ]
Make blocks resistant to water or lava or take their resistance away and configure water and lava behaviour.
Installation
- Download and install NBTLib 0.3 or higher.
- Download and install the WaterProof.jar.
- Start your server.
Commands
/waterproof - Shows the help
/waterproof version - Shows the current version
/waterproof reload - Reloads the configs
Permissions
waterproof.all - Lets you use the /waterproof command and notifies you when an update is available.
Dev Builds
Quote:Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk!
[ Dev Builds ]
@palyons
This means that NBTLib is not installed.
Ok, so once again, here is the error I get when trying to run Latest build of WaterProof, with Latest CraftBukkit 1.6.1 Dev build: 10:17:13 [SEVERE] Could not load 'plugins/WaterProof.jar' in folder 'plugins' org.bukkit.plugin.UnknownDependencyException: NBTLib at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:195)
@palyons
NBTLib was designed to provide independence for other plugins. And unless something very bad happens, it is always up to date. ;)
Ok, so WaterProof has been updated for 1.6.1. But I can't currently use it with the latest dev build of CraftBukkit, since it depends on NBTLib, which isn't updated yet.
@palyons
55 = Redstone wire (block).
Since WaterProof is working with blocks, you have to use block values. ;)
@Siguza the following is my config.yml file: check-update: 'true' allow-event-cancel: 'true' allow-water-in-nether: 'true' water: proof: &id001 - '55' - '75' - '76' break: [] lava: proof: *id001 break: []
I know that redstone wire/dust is id 331, and that's not in the list. but as far as I can tell, the lava isn't hitting the redstone, like it should be, causing the obsidian to create. If needed, I can record a video later tonight showing what happens.
@palyons
You didn't mention the actual bug I think. Are obsidian generators broken? And if yes, is it possible that redstone wire is in the water-/lavaproof list?
Discovered possibly another bug. This one seems to affect obsidian generators. The best way I can describe it is to show this tutorial: http://www.youtube.com/watch?v=FBg5or1-HiQ Normally I wouldn't be concerned about it, but some of my players on my server like to use the generators. Thanks again!
@Siguza, Awesome. Thank you very much! Just tested out the latest dev build with the fix and it works wonderfully.
@palyons
Bugfix is on the way. :)
I found a fairly large glitch with this plugin. While it works fine for placing and breaking blocks with water and/or lava. When you try to dispense a water or lava bucket out of a dispenser, it dispenses the Water Bucket or Lava Bucket Item, and not the water itself. This causes a lot of problems since my farms are dependent on dispensers.
@CommodoreAlpha
Shame on me, I forgot to add 256 to the item ID. Fix is coming.
It appears I get this error when I run both RecipeManager and WaterProof, and when I asked the developer of RecipeManager about the error, he redirected me here.
(Ignore the last two lines of the error log.)
And since I don't know any code, I'll just quote him for clarity:
@LastTulare
Fixed in v1.1.2
It keeps flowing water from mowing down redstone items, but if you place water buckets on the item itself, such as a rail it will break it :( That is If youre an admin placing water on an LWC locked rail! its all good here, this plugin is boss! <3
@CommodoreAlpha
The &id and *id stuff is actually just YAML, but I guess you can't expect people to really know it... I added it.
@Siguza
You should include (in bold red words) in the configuration explanation that "*id001" links to "&id001", and that "*id001" should be removed if you want to add blocks to the "lava proof" list, because it will reset your configuration otherwise (and might cause anger). Lucky for me though, I keep backups of whatever I configure, so I never get angry at reset configurations.
And I'll bug Intelli about logging the SweepAwayEvent. I assume he probably forgot and needs to be reminded. Sorry for bugging you, and thanks for the response. :P
@CommodoreAlpha
For some reason, whenever I try to add any block to the "lava proof" list, the plugin resets my configuration.
Here's the report, which contains the error and my configuration.
Also, does the SweepAwayEvent apply to lava too? CoreProtect still isn't logging blocks broken by lava; I don't know if it's because Intelli didn't add the ability to log the new event, or if it's because SweepAwayEvent doesn't include lava.
@CommodoreAlpha
Added it in the description.