Protection and Break Sources
Stopping a regenerating block from being touched, and what else can break it.
Two related settings groups live in config.yml. sources controls what is allowed to
start a regeneration in the first place, protection controls what is blocked while a
block is mid-regen.
Break sources
Player breaking is the only source switched on by default. The other three exist and work fully, they just ship off, since not every server wants explosions or mobs triggering regen.
| Key | What it allows | Default |
|---|---|---|
sources.player-break | A player breaking the block | true |
sources.explosion | Explosions destroying it | false |
sources.piston | Pistons pushing or pulling it away | false |
sources.mob | Mobs griefing it | false |
Protection while a block is pending
While a block is waiting to regenerate, each of these is its own toggle:
| Key | What it stops | Default |
|---|---|---|
protection.block-break | Players breaking the temporary block | true |
protection.block-place | Players placing a block on that spot | true |
protection.piston | Pistons pushing or pulling it | true |
protection.explosion | Explosions destroying it | true |
Protection and break sources are separate settings. Turning on sources.explosion
lets an explosion start a regeneration cycle on a handled block. protection.explosion
is what then stops a second explosion from destroying the temporary block while it
waits to come back.
Strict lock
protection.strict-lock, on by default, is a stronger lock than protection.block-break
and protection.block-place. While it is on, nobody can break a pending placeholder or
build on its spot, in any game mode, an op or someone with regenzones.bypass included.
The one way past it is disabling the region itself with /rz toggle <name> off.
It exists because the most common way to test a zone is as an op, and an op silently
bypassing the lock reads as the lock not working. A placeholder that is a fresh crop, a
CARROTS[age=0] replace-with in a farm zone, only makes sense if it cannot be harvested
early.
Staff bypass
regenzones.bypass ignores the four protection toggles above, for staff who need to work
inside a region without being blocked by its own rules. It only takes effect once
protection.strict-lock is set to false.
Strict Creative mode lock
protection.strict-creative-lock is the narrower, Creative-only version of the strict
lock, from before the full one existed. It only matters when strict-lock is off: it then
denies breaking a pending block in Creative mode for everyone, bypass or not, while
survival keeps the staff bypass.
This exists because Creative mode digging is client-predicted, the client removes the block visually before the server confirms it, unlike survival's server-authoritative digging. RegenZones resyncs the block with the client immediately so turning this on never leaves a visual gap where the block briefly looks gone.
Support and liquids
protection.physics, on by default, keeps a placeholder standing when the block it sits
on goes away or a liquid flows into its spot. Without it a crop placeholder pops off as an
item the moment its farmland is broken or trampled, and a torch placeholder washes away
under water, both without any break event to deny. With it on, the placeholder stays put
until its restore, and water or lava stops at the edge of a pending spot.
This also applies to an AIR placeholder. Water will not flow into a mined-out spot
while it is waiting to come back. Set physics: false if a zone relies on that.
Growth
protection.growth, on by default, stops a placeholder growing on its own. A
WHEAT[age=0] placeholder on lit, watered farmland is still a real crop to vanilla, and
random ticks or bone meal would otherwise grow it to full size while it is still locked,
where it looks like ripe wheat that refuses to break. With it on, crops, stems, sugar cane
and cactus do not grow on or into a pending spot, bone meal does nothing there, and a
sapling placeholder does not turn into a tree. A tree growing nearby still grows, minus any
block that would land on a pending spot.
Placeholder growth stages are unaffected, those are written by RegenZones itself.
Deny messages
Holding the mouse on a locked crop fires a break attempt every few ticks, and each one used
to send a chat line. protection.deny-message picks where the "that block is locked"
messages go, ACTION_BAR above the hotbar by default, CHAT, or NONE to say nothing.
protection.deny-message-cooldown, 3s by default, is the shortest gap between two of
them to the same player, whichever place they go.
protection.deny-message-grace, 2s by default, keeps quiet about a placeholder that only
just went in. A crop breaks in one hit, and holding the mouse down swings again a few ticks
later at whatever the crosshair is on, usually the fresh placeholder of the crop just taken.
That swing is still refused, it just does not say so, since a message there reads as if a
normal crop would not break.
Held digs
A crop breaks in one hit and the client predicts the break itself. Refusing it hands the
placeholder straight back, and with the button still down the client breaks it again the very
next tick, so the crosshair never gets past the spot. protection.dig-guard, 2s by default,
refuses every break on a placeholder that young before any other plugin sees it, ops and
bypass holders included, and keeps refusing for as long as that player keeps swinging at it.
For an instant-break placeholder (crops, flowers, saplings) the player swinging sees the spot
empty, the way a harvested vanilla crop looks, so the crosshair moves on to the next crop.
The world never changes: the placeholder is still there, and it shows again on their screen
half a second after the swings stop. 0s turns this off.