Protection Rules

Protection Rules is where every detection is switched on or off and told what to do when it fires. What each individual detection actually looks for is listed in the Detections reference. This page covers the controls around them.

Finding a rule

Rules are grouped into category tabs and one category is shown at a time. On resource 1.5.9.4 and newer the categories are Main, Player Stats, Resources, Entities, Events, Weapons and Pyrotechnics. Older servers keep a flat layout and everything lands under one tab.

• Search spans every category at once, so you do not need to know where a rule lives.
• Filter: All, On, Off. Filtering to Off is the quickest way to see what you are not running.
• Sort: enabled first, disabled first, or by name in either direction.

A rule card

Each card has the rule name, an information button, and on the right:

• The action pill, showing kick or ban. Click it to switch. It only appears while the rule is enabled, and only on rules that have an action at all.
• The master toggle for the rule.

The information button opens a plain-English description of what the rule watches for. Read it before switching a rule to ban, because the cost of a false positive on a ban is a great deal higher than on a kick.

Per-rule options

Everything a rule carries beyond its enable and action is shown inline on the card, so there is no hidden second screen. The shapes you will meet:

• Toggles for sub-detections, usually under a Types block. A rule can watch for several different behaviours and each one switches on its own.
• Numbers, typically a threshold and a time window. Raising a threshold makes the rule fire later and less often, which is the standard way to quiet a rule that is catching legitimate activity.
• Whitelist lists, for weapons, events, resources, models and similar. Adding an entry lets exactly that thing pass without tripping the rule, which is far more surgical than switching the whole detection off. A false positive from one of your own scripts almost always belongs here.
• Whitelist zones on a couple of rules, where each entry is a sphere of the map the rule ignores.
• Spam rules on the entity, explosion and particle spam protections from resource 1.7.2 and newer. Up to five numbered rules, each with a type, a threshold and a time window. Rules are always numbered from one with no gaps, so deleting one renumbers the rest. Deleting the last rule for a type also switches that type off, since a type with no rules does nothing.

The one thing the editor will not let you do

A rule built out of a Types block cannot be enabled while every type inside it is off. The toggle refuses and tells you to enable a type first. That is not a limitation, it is stopping a rule that would sit there looking enabled and catching nothing.

Reset to default

The header button loads the recommended configuration for your resource version. It replaces your detection settings with ours, including every whitelist you have built up, so treat it as a fresh start rather than a repair. It is not scoped to this page either: the whole configuration is replaced, so your Main Settings go back to defaults too. The Discord webhooks are carried over, and the global-ban switch and its whitelist are untouched because they live outside the config. Like everything else on the page it is only an edit until you press Save Changes, and Reset on the save bar puts your settings back.

Saving and permissions

• Nothing writes as you toggle. The Save Changes bar at the bottom does the writing.
• A save that touched the detections writes a protection rules row to the activity log with your name on it.
• The new configuration is pushed to a connected resource straight away, and an offline server picks it up when it reconnects.
• Reading this page needs the settings view permission, and changing anything needs settings edit. With view only every control is visible and disabled, which is intentional: an admin should be able to see how the server is configured before asking for a change.