FAQ

Yes. It targets the plain Spigot API so it runs on Spigot and Paper alike, nothing Paper-only is used anywhere in the plugin.

No. WorldEdit and FastAsyncWorldEdit are optional. If either is installed, RegenZones can read your WorldEdit selection when you have no plugin selection of your own. The wand and /rz pos1 / /rz pos2 work fully without them.

Nothing is lost. Pending blocks live in storage (SQLite or MySQL), not in memory. On the next start, anything whose timer already ran out is restored straight away, and everything else keeps counting down from where it left off. See Regeneration Engine.

No. Restores are batched by regeneration.blocks-per-tick in config.yml, which caps how many blocks come back in a single tick.

Yes. It stores the full block data of whatever was broken, including a crop's growth stage, so a crop comes back exactly as it was, not just replanted at stage zero.

Do not add chests to a region's rules. They are not in any shipped group, and if you use a * wildcard, add CHEST to that region's excluded list. Only block data is captured, not what is inside a container, so a restored chest would be empty.

Yes. regenzones.bypass ignores every protection check for whoever holds it.

The one with the higher priority number. If both regions share the same priority, the one created first wins. See Selection and Regions.

Yes, /rz menu opens one, covering everything a command can do short of creating or redefining a region, which both need a selection first. See Config GUI.

Yes, if ItemsAdder is installed. Name the custom block's namespace:id anywhere a material normally goes. See Block Rules.

Yes, flag the region with /rz farmland <name> on. Its farmland stops drying out or getting trampled back to dirt, and its crops keep growing on a timer of their own, no light or water needed. See Farm Zone.