Blacklist events not properly assigning to blocks.
LadyCailinBot opened this issue ยท 3 comments
WORLDGUARD-3939 - Reported by mrcoffee1026
Example 1: bedrock:
[bedrock]
on-break=deny
on-destroy-with=deny
on-place=deny
on-interact=deny
on-drop=deny,tell
on-acquire=deny
on-dispense=deny
Bedrock is given to players by logblock as a tool to use, so it needs to be "use-able", but otherwise... this should be fine. Except that this also effects the block on top of the bedrock as found naturally in the game. If you mine down to bedrock you cannot place blocks on top of bedrock? This should not be true. I should be unable to PLACE bedrock, but setting "on-place=deny" should not have any effect on blocks being placed on top of a blacklisted block.. why does it?
Example 2: gold_block,lapis_block:
[gold_block,lapis_block]
#on-use=deny
on-interact=deny
I found I had to take ridiculous extra steps due to a misbehaving plugin - Vampires - in which you craft an altar with these blocks and "infect" yourself... which is normally the intended behavior... but not mid-event in a creative world. However, setting "on-use=deny" makes gold blocks unplaceable... there is a seperate "on-break" for that, Why is "on-use" causing the block to be unplaceable? And... same issue as before. not blocks can be placed on top of a gold block with either of the settings "on-use" or "on-interact" denied. Again, why? That is not working as it should. Despite this having been done, the blocks can still be used as altars in creative... so the misbehaving plugin has some very simple way around this, clearly... but the blacklist itself is not working the way it should, so should still be remedied.
Can confirm, the following settings will ban players that place blocks near bedrock or use buckets to gather lava above bedrock.
[bedrock]
on-break=deny,log,notify,ban
on-place=deny,log,notify,ban
on-drop=deny,log,notify,ban
on-acquire=deny,log,notify,ban
original issue is intended behavior as they denied interacting with bedrock (e.g. placing a block against the bedrock by right clicking the bedrock)
can't reproduce your issue antal. possibly turn on debug logging to see why a break/place would get fired for bedrock if they are not placing/breaking bedrock
for reference, this is what happens when you place a grass block on bedrock:
[11:17:35] [Server thread/INFO]: [WorldGuard] INTERACT BEDROCK [CraftPlayer{name=wizjany}] @-97,73,-80 : PlayerInteractEvent.RIGHT_CLICK_BLOCK [ALLOW]
[11:17:35] [Server thread/INFO]: [WorldGuard] USE GRASS_BLOCK [CraftPlayer{name=wizjany}] @world : BlockPlaceEvent
[11:17:35] [Server thread/INFO]: [WorldGuard] PLACE GRASS_BLOCK @-97,73,-79 [CraftPlayer{name=wizjany}] : BlockPlaceEvent
as long as there's no on-interact= in the blacklist for bedrock this is totally fine.