Self descriptive, much similar to #2395

See screens - all steps are clearly visible

Logs:
latest.log
debug.log
modlist.txt

Doesn't matter if perm-s defined for zone or globally
https://www.dropbox.com/s/2xerwwsou2nrnx0/%D0%A1%D0%BA%D1%80%D0%B8%D0%BD%D1%88%D0%BE%D1%82%202019-02-15%2006.09.44.png?dl=0

Same is true for water

/p group GUESTS zone tst1 deny fe.protection.use.minecraft.lava_bucket.*
/p group GUESTS zone tst1 deny fe.protection.use.minecraft.water_bucket.*
do not work

Please test this on 1.7.10 and compare

I used the same solution 1.7.10 used for use item

Also, verify that other deny fe.protection.use blocks other item usage.

Hmmm, I'm not sure that I can test it on 1.7.10 any time soon - shouldn't we just focus on the latest supported version instead?

I found out that lava restriction also cause server internal error (one I mentioned on discord on Feb-15), will do more testing and record some videos.

Placing and breaking block protection works fine as far as I can tell.

Aha, I got it -
fe.protection.exist.minecraft.lava_bucket and fe.protection.inventory.minecraft.lava_bucket just throw user out and won't allow him to join if he has lava bucket in his inventory. It may be "as intended" behavior...

But following nodes just do nothing:

• fe.protection.use.minecraft.lava_bucket
• fe.protection.place.minecraft.flowing_lava
• fe.protection.place.minecraft.lava
• fe.protection.trample.minecraft.flowing_lava
• fe.protection.trample.minecraft.lava

Ah, nope - Here it says it should drop/destroy items, not ban players.

So all 3 nodes do not work as intended: use, inventory and exist

Here's the videos:

1. Trying to restrict lava use @6:46 you can se it threws player out (instead of destroying the item).
2. More thoughts just ignore comment about ALL guests, it's not true, it won't let in only guests with lava.

As for "inventory" node - in 1.7.10 it works (as stated by Jelaw21 on discord - it drops items). On 1.12.2 it threws player out (
I guess it worked properly on 1.8.9 too (if I remember correctly)

Main reason for comparing with 1.7.10 is that most items still worked on 1.7.10 so if we know it works we can narrow down the timeframe that the bug occurred to being caused by the port to 1.10+.

When it will be fixed?