Plugin support
WorldGuard
RP Engine hooks into WorldGuard to keep custom content out of the places your regions already protect: a spawn where nobody may put models down, an arena where custom items do nothing.
RP Engine has no protection of its own and is not trying to grow any. It knows whether something can physically happen, never whether it is allowed to, so a server with regions says where using content is allowed the same way it says where building is.
Two region flags, if WorldGuard is installed:
/rg flag spawn rpengine-place deny
/rg flag arena rpengine-use deny| Flag | Covers |
|---|---|
rpengine-place | Putting a model down, and breaking one |
rpengine-use | Using a custom item |
Both allow by default, so installing WorldGuard changes nothing until you set one.
It fails open#
Anything that goes wrong allows
A flag that never registered, an exception, WorldGuard not answering, a player with bypass — all of them allow.
A protection hook that failed closed would lock a server out of its own content the moment anything went wrong with it, which is a worse outcome than an unguarded region. You would find out from players who cannot place anything anywhere, with a stack trace nobody saw.
Why this needed no engine change#
The whole integration is a listener cancelling
events RP Engine already fired: ModelPlaceEvent,
ModelBreakEvent, ItemUseEvent.
That is what those events are for. A region check baked into placement would have locked every other protection plugin out of the same decision — and the same events are why GriefPrevention, a claims plugin or your own rule can do exactly what WorldGuard does here, without waiting for us.
Placement already respects protection#
Separately from the flags: a placement asks the server whether that player could have placed a block there.
So spawn protection, world protection and most claim plugins already apply with nothing configured. The flags are for the case where you want models and items treated differently from blocks — a region where building is fine but statues are not.