Skip to content

Configuration

Ghost edited this page Nov 15, 2026 · 1 revision

⚙️ Configuration and Data Storage

The supplied Fabric Guard 1.7.10 implementation uses JSON files for its configuration, blacklist and saved regions.

Main configuration

Location (relative to the server directory):

config/fabricguard/config.json

The inspected binary writes these defaults on first run:

{
  "usePlayerMoveEvent": true,
  "maxRegionCountPerPlayer": 7,
  "maxRegionBlocksPerPlayer": 0
}
Key Default Description
usePlayerMoveEvent true Controls a movement-event-related option in the configuration.
maxRegionCountPerPlayer 7 Configured region-count limit for players.
maxRegionBlocksPerPlayer 0 Configured limit value for region blocks; do not assume 0 means a particular limit policy without testing the command path.

Only the above three values are written and read by the inspected configuration class; avoid adding unsupported options copied from WorldGuard's Bukkit config.

Blacklist

config/fabricguard/blacklist.json

See Blacklist-and-Protection for the supported JSON format.

Region storage

Each dimension has its own regions.json file under a fabricguard directory within the world save. In the inspected build, the path is constructed from the world root plus the dimension location.

Common examples:

<world-folder>/fabricguard/regions.json
<world-folder>/DIM-1/fabricguard/regions.json
<world-folder>/DIM1/fabricguard/regions.json

Custom modded dimensions use a dimension-specific path constructed from their namespaced identifier. Treat the examples as typical; verify the actual save layout.

Stored region data includes geometry, priority, owner/member domains, flags and parent relationships. Editing these files while the server is running can be overwritten by in-memory changes.

Saving and reloading

/rg save
/rg reload

The following utility command also reloads mod configuration and region data:

/fabricguard reload

Backups and updates

  1. Stop the server, or create a consistent backup after /rg save.
  2. Back up the entire world folder and config/fabricguard/.
  3. Keep a copy before upgrades or manual JSON changes.
  4. Use a staging server to test new mod versions or cross-version migration.

A damaged or invalid JSON file may trigger a log error. Do not delete the only copy of region data while troubleshooting.

Clone this wiki locally