Wiki Release: 2026.09.5 · UltimateOutpost: 1.27.1 · Documentation branch: 1

Capture and ownership#

Capture lifecycle#

An outpost has a configured region and capture state. Eligible players/groups contest that region until the plugin decides a new controller/owner. Ownership is then used by player commands, statistics, advantages and integrations.

During staging, test with two groups so you can observe both successful ownership and a contested transition.

Verify the region before benefits#

Use /uoutpost view <name> and /uoutpost tp <name>. Walk every edge of the intended capture area. A region that is one block off can look like an advantage failure because the expected group never actually became owner.

Abandon#

/outpost abandon is the player-facing release flow in the supplied command tree. Test it with the current owner and verify that the resulting unowned state persists after restart.

Group integration#

UltimateOutpost supports multiple external group systems through extensions. Test the same group implementation used on production. If a capture works as a standalone player but not as a group, diagnose the group adapter before changing the outpost region.

Persistent state#

Use plugin commands/maintenance actions rather than manually editing the SQLite/storage data while the server is online. Ownership can be cached by runtime managers and direct database edits may leave memory and disk out of sync.