Multiple issues with Grief-Revert fields
Opened this issue ยท 2 comments
There are three major issues I've been having with my grief revert fields lately.
- All blacklist options on grief revert no longer work. Grief-revert.black-list does nothing, even with the default settings that block cake. The Allow-Grief flag also does not work.
- Grief Revert fields are now considered translocation fields and block other fields from being placed within their area. This can by bypassed by disabling the field, placing the new fields, and enabling it again. (This doesnt seem to cause any issues, but is very inconvenient to users)
- When using the Place-Grief flag, users can destroy blocks and then replace them with dirt or cobble to prevent them from being reverted. Normal block placement is reverted, but when they fill the damage with another block type it stops it from being changed back to the original material.
I can provide a list of plugins running on my server if needed, however the list is quite long and I would rather wait if you need them before I put them here. We are currently using the latest build of precious stones (9.6.0) and bukkit version git-Bukkit-1.5.2-R1.0-25-g2a13a5a-b2812jnks (MC: 1.6.2).
P.S: I would love it if you made the bypass-blocks list possible to be used as field blocks as well, so players could place offensive and healing stones inside of other peoples protection fields during pvp.
I have made a temporary workaround for the translocation bug by editing the code in PSBlockListener.java, and commenting out the following section at lines 1481 to 1490:
// cannot place field in grief revert fields
/*field = plugin.getForceFieldManager().getEnabledSourceField(block.getLocation(), FieldFlag.GRIEF_REVERT);
if (field != null)
{
ChatBlock.send(player, "translocationNoFields");
event.setCancelled(true);
return false;
}*/
I do not use translocation blocks at all, so I am hoping this has no effect. This measure could also be bypassed by disabling grief revert fields temporarily when placing new fields, and then enabling them again.