Dominion

Start here

Players: read the player docs to learn about point selection, claim creation, member collaboration, permissions, and the UIs. Administrators: read the admin docs for installation, database, configuration, limitations, migration, backup, and troubleshooting. If you need to use it immediately, start with the player overview. When deploying a server, start with the admin overview and installation and upgrades.

Core features

Dominion splits a Minecraft claim into four objects that can be managed separately:

Object	Role	Typical location
Claim boundary	Stores the world, 3D coordinates, parent/child hierarchy, and teleport point	In-game UI or /dominion commands
Environment rules	Control mobs, explosions, fire, fluids, and redstone-related environment behavior	flags.yml + claim environment flags
Member permissions	Control what guests, members, and permission groups can do with blocks, containers, interactions, movement, and combat	Claim UI, members, permission groups, templates
Server policy	Controls the database, creation limits, economy, world-wide rules, and UI defaults	config.yml, limitations/, world-wide/

This separation means that “can a player open a chest” and “can mobs spawn inside the claim” are two different kinds of settings. Before changing permissions, first determine whether the problem belongs to the claim boundary, membership, a permission flag, or a server limit. That avoids repeatedly trying the wrong configuration file.

Pages

Task	Page
Create your first claim, expand it, and set a teleport point	Player: claim workflow
Choose ChestUI or Dialog	Player: the two UIs
Give friends chest, button, or build access	Player: members and permissions
Look up complete command syntax	Player: command reference or Admin: commands and operations
Install the plugin and confirm it loads	Admin: installation and upgrades
Change the database, default UI, messages, and border display	Admin: config.yml
Tune every available flag	Admin: flags.yml and flag design
Limit claims per player, sizes, and teleport cooldowns	Admin: limitations
Set default rules for unclaimed areas	Admin: world-wide
Errors, permissions not applying, or Dialog unavailable	Admin: troubleshooting

Important safety boundaries

Claim deletion, ownership transfer, database import, and configuration migration can be irreversible or have wide-ranging effects. Before performing these operations, export the database or copy plugins/Dominion/, and do not copy limits verified on a test server directly to production. The confirmation prompts for /dominion delete and /dominion give are not decoration; they prevent accidental operations.

dominion.admin, which administrators hold, can bypass claim limits and part of the permission checks by default, but that is not the same as “regular players have every permission”. If an administrator needs to test guest behavior, use a test account without OP or dominion.admin, or let an administrator configure the server and have a regular account verify the result.

Sponsorship

Dominion is a continuously maintained open-source project. If you would like to support the project, visit the sponsorship page. Sponsorship benefits and implementation boundaries are described in Sponsorship.