Permissions

Admin nodes

sndtc.admin grants all of these. Give them individually to hand out part of the surface.

Making cores staff-only

Revoke sndtc.break. A player without it is told once, on their first click, that they may not break the core, and the click is cancelled so no breaking animation starts. Repeated attempts are rate-limited to one message every three seconds, so holding the mouse button down does not flood their chat.

The message they see is messages.no-break-permission in lang/messages_en.yml.

Cores inside protected regions

This is the one place the permissions interact with another plugin. A protection plugin cancels the left click inside its regions, and a cancelled left click means the client never starts breaking - so without special handling, a core inside a spawn region would simply be immune.

SnDTC un-cancels that click for an active core when the player holds sndtc.break. That single step is the entire region compatibility: there is no WorldGuard dependency and nothing to configure. Cores are meant to live in protected areas, so this is the normal deployment.

A consequence worth knowing: because SnDTC deliberately overrides another plugin's veto on a core block, a jail, freeze or spectator plugin cannot stop a specific player from damaging a core. sndtc.break is the gate for that.