Skip to main content

Set Residence visitor flags without locking out the owner

Residence applies protection flags to a defined area, with separate player and group overrides. Diagnose access from the claim where the problem occurs. A visitor who cannot build may still have another form of access through an override, and an owner using administrative commands can bypass the restrictions you intend to test.

Inspect the claim before changing it

Use the supported Residence build for your Minecraft release and check required dependencies from that release. Keep the current configuration and protection data before adjusting existing rules. These steps assume you own a small test residence or have permission from its owner. They do not require deleting a claim or changing the server's global defaults.

Stand inside the intended claim and use /res current, /res info and /res show. Confirm its name, owner, world and visible bounds. A subzone can have different rules, so note whether you stand in the main residence or a named subzone. Record current flags before saving any edits.

Choose the rule that matches the action

  1. Use /res flags and the official flag reference to identify the setting for the reported action. Building, containers, movement and interactions are different tests.
  2. Inside your test residence, use /res set build false to trial general building protection. The command acts on the current residence; verify your location first.
  3. Use /res check ResidenceName build VisitorName, replacing both names, to inspect the effective value for the visitor.
  4. Ask that non-operator visitor to try placing and breaking disposable blocks inside the claim, then outside its boundary.

If visitors need to walk through a shop but should not use storage, preserve movement access while reviewing the documented container flag. Avoid toggling the movement flag during a public event; it can prevent legitimate visitors entering or leaving as expected. Test doors, buttons and other interactions using the exact block types your build contains.

Review individual overrides

Use the claim information and applicable group settings to find an explicit exception. Residence supports player rules through /res pset, group rules through /res gset, and removal of a local flag value. Review an override before adding another one. A broad trusted-player grant can undermine a narrow container restriction.

Run the tests with the owner's normal permissions too. Use /res for the trial rather than /resadmin, which the command documentation identifies as the administrative form. Keep console or another authorised staff member available in case a mistaken flag prevents normal access.

Undo only the test

Return a changed flag to its recorded previous value. Use remove only when you intend to remove the local setting and allow the applicable defaults or inheritance to take effect; it does not mean the same thing as setting false. Retest both visitor and owner afterwards.

Do not run /res clearflags or delete the residence to fix one denial. Those actions discard unrelated protection choices. If the result remains wrong, collect the residence and subzone names, coordinates, flag check output and plugin versions. Keep staff permission exports and private configuration out of public chat.

back up the server files · review LuckPerms groups and inheritance · collect the relevant Minecraft logs

Official references

No comments to display