Protection Flags

LWC has multiple protection flags which enhance similar block protections in very specific ways. You get the flag values of a block with the command /cinfo.

Magnet

Chests and other blocks with inventories can become magnetized to allow them to suck in items from around them (default radius: 10 blocks). This flag can be configured and also disabled by editing the magnet.yml.

This is most useful for automatic farms and "mob traps", where you can collect items without actually picking them up with hoppers or being beside the trap / farm the entire time.

• Command: /lwc flag magnet <"true" or "false"> or /cmagnet <"true" or "false">

• Permission: lwc.flag.magnet

Redstone

By default, this flag will disable redstone mechanics on the protections. The default behavior you can configurate in the core.yml:

protections:
    # If true, the default behaviour will be to BLOCK redstone to protections, and /credstone on (Protection Flag)
    # will ALLOW redstone to the protection
    # If false, the default behaviour will be to ALLOW redstone to protections, and /credstone on will
    # BLOCK redstone to the protection
    denyRedstone: false

The redstone flag either disables or enables redstone use on the protection.

Warn: In the last time, a bugreport about the redstone flag behavior was reported on Github, so the flag can be a little unintuitive at the moment: #159.

• Command: /lwc flag redstone <"true" or "false"> or /credstone <"true" or "false">

• Permission: lwc.flag.redstone

Autoclose

This flag allows to auto-close protected doors / trapdoors after a short time. If you have a double door (by default LWC open both, if one's is protected) it's better to set these flag for also booth doors separately.

Note: The behavior of doors / trapdoors you can configure in the doors.yml.

• Command: /lwc flag autoclose <"true" or "false"> or /cautoclose <"true" or "false">

• Permission: lwc.flag.autoclose

Allowexplosions

By default, protected block get also destroy with explosions. With this flag you can prevent or allow the block destruction at explosions.

• Command: /lwc flag allowexplosions <"true" or "false"> or /callowexplosions <"true" or "false">

• Permission: lwc.flag.allowexplosions

Hopper flags

Note: The option disable-move-event in the paper.yml must be set to "false". In some situations these paper option can be help to improve the performance and decrease lags by hopper actions. But the LWC hopper flags need this event to work.

By default, hoppers can not interact with protections to prevent griefing. The default behavior you can configurate in the core.yml:

protections:
    # If true, hoppers will by blocked by DEFAULT and /chopper on will enable hopper use on them
    # If false, hoppers will be enabled by DEFAULT and /chopper on will disable hopper use on them
    denyHoppers: true

The hopper prevention is not dependent on the gamemode, hopper slot or the fill item / his amount.

Hopper

This flag sets the hopper behavior when they're built to insert / extract items from protected inventory blocks, such as chests.

Note: The "Hopperin" and "Hopperout" flag are childrends of the "Hopper" flag. Activate the behavior with a activation by one of them. Deactivate the behavior with a deactivation of the "Hopper" AND the "Hopperin" / "Hopperout" flag.

• Command: /lwc flag hopper <"true" or "false"> or /chopper <"true" or "false">

• Permission: lwc.flag.hopper

Hopperin

This flag sets the hopper behavior when they're built to insert items from protected inventory blocks, such as chests.

Note: This flag is a child of the "Hopper" flag. Activate the behavior with a activation by one of them. Deactivate the behavior with a deactivation of the "Hopper" AND the "Hopperin" flag.

• Command: /lwc flag hopperin <"true" or "false"> or /chopperin <"true" or "false">

• Permission: lwc.flag.hopperin

Hopperout

This flag sets the hopper behavior when they're built to extract items from protected inventory blocks, such as chests.

Note: This flag is a child of the "Hopper" flag. Activate the behavior with a activation by one of them. Deactivate the behavior with a deactivation of the "Hopper" AND the "Hopperout" flag.

• Command: /lwc flag hopperout <"true" or "false"> or /chopperout <"true" or "false">

• Permission: lwc.flag.hopperout

Exemption

This admin flag allows you to exempt the block from the Protection Cleanup Commands "Purge by Activity" and "Purge by Player".

• Command: /lwc flag exemption <"true" or "false">, /lwc flag exempt <"true" or "false"> or /cexempt <"true" or "false">

• Permission: lwc.flag.exemption