Repository navigation
Owners and Members
Fabric Guard supports two region roles: owner and member. Owners and members are tracked in each region's saved data and can influence region permission checks and group-targeted flags.
| Action | Command |
|---|---|
| Add owner | /rg addowner <region> <player> |
| Remove owner | /rg removeowner <region> <player> |
| Add member | /rg addmember <region> <player> |
| Remove member | /rg removemember <region> <player> |
Example:
/rg addowner town AdminPlayer
/rg addmember town BuilderPlayer
/rg removemember town BuilderPlayer- Owners are trusted region controllers and are included in owner-related checks.
- Members are trusted participants in member-related checks.
- The mod also recognizes permission-group entries in region domains; specific results depend on the configured permission provider and each flag's behavior.
- These roles are not equivalent to full server operator access or permission to run every administrative command.
When creating a normal cuboid region, the selecting player is automatically registered as an owner in the inspected build.
You can deny entry to nonmembers while allowing authorized people through. See Entry-and-Exit for supported groups and commands.
The 1.7.10 implementation resolves player names through the server's available player information. If an offline player's name is not resolvable, use an online player or check server player-cache behavior. Do not assume every unknown username can be added successfully.
Grant ownership only when needed. For temporary access, prefer adding a member and configuring the required flags instead of granting all server-level bypass permissions.
See also Permissions and Region-Priority-and-Parents.
Fabric Guard 1.7.10 · Modrinth · CurseForge · Home · Troubleshooting · Discord
Independent Fabric region-protection mod; not the official WorldGuard plugin.
🛡️ Fabric Guard Wiki
Regions
Protection
Help