Claims & Parties (Open Parties and Claims)

Nytheria protects land with Open Parties and Claims: Team Claims, which is Open Parties and Claims (OPAC) by Xaero96 plus a Team Claims layer written for the pack. This page belongs to the Multiplayer hub. It explains what you can claim, how a party shares claims, and what a claim does and does not protect. There is no FTB Chunks in the pack.

How it works#

A claim is one chunk of land that you protect. Inside your claims other players cannot break, place or use things unless your settings let them. You claim from the world map, from the claim menu or with commands. OPAC draws claims on both the minimap and the world map.

There are two kinds of claims, and they use separate budgets:

Private claims belong to you. You get 500 chunks and 10 forceloaded chunks.
Team claims belong to a team. A team needs at least two members before it has any. Neither budget counts against the other.

A party is a group of players who trust each other. OPAC keeps its own party list and mirrors it with FTB Teams in both directions. If the two disagree, OPAC wins. Allies, colour, description and party chat are not synced, and the sync option is read when the server starts. Parties are the same ones that share your quest progress, so one /ftbteams party create is enough for both.

OPAC reads its limits and admin rights through FTB Ranks. In singleplayer and LAN worlds there are no ranks, so only the numbers below apply.

Numbers and settings in Nytheria#

Per-player limits#

Setting	Value	What it means for you
Claims per player	500 chunks	Your private budget
Forceloads per player	10 chunks	Chunks that stay loaded while you are online
Claim distance	25 chunks from you	You can claim up to 25 chunks away (the mod default is 5)
Chunks per action	121 (11 by 11)	The largest area for one claim, unclaim or forceload
Touching claims	allowed	Your claims may sit next to each other
Claimable dimensions	all	Every dimension can be claimed
Player claims expire after	8,760 hours (365 days)	Expired claims turn into "expired claims"
Parties expire after	720 hours (30 days)	Inactive parties are deleted
Party size	64 members, 64 allies, 16 invites	OPAC's own limits

Claims are not tied to an anchor block, because anchor-based claiming is off.

The team pool#

Team size	Team claims	Team forceloads
1	0	0
2	500	10
3	525	12
4	550	14

The formula is 500 claims plus 25 per member beyond two, and 10 forceloads plus 2 per member beyond two. A team of one has no team claims, although its private budget still applies.

More settings of the team layer:

Setting	Value	What it means for you
Team forceload grace	0 minutes	Team forceloads are released as soon as the last member logs off
Over-limit grace	168 hours (7 days)	A team above its limit has 7 real days before the newest team claims are unclaimed
Convert radius	4 chunks at most	Largest area for one conversion between private and team claims
Team name	up to 24 characters
Territory messages	on by default	A message appears when you enter or leave team land

What a claim protects#

These are OPAC's defaults for new players; the pack does not override them:

Rule	Value
Claimed chunks are protected	yes
Full access	members of your party
Fluids, pistons and dispensers from outside	blocked
Hostile and friendly natural spawns inside	still allowed
Player-versus-player combat inside	allowed
Explosions and fire	no exceptions
Personal forceloads	need the owner online
Party members on the map	shown (location sharing on, allies off)

The server config adds exceptions. Anyone can use a crafting table in a claim. Minecarts are exceptions, and all friendly entities except boats are protected. No hostile mob is protected. The Supplementaries slingshot is a banned item, and fireworks are allowed. Several access groups, such as villagers, trade, item frames, armor stands, doors and chests, are optional exceptions you can set per player.

Step by step#

Claim your base#

Open the claim menu from the shared P key (a Polybind wheel with Social Interactions, FTB Teams and Open Parties and Claims), or open the world map and use its claim tool.
Select the chunks and claim them. You can also run /oclaims claim, with optional area arguments.
Use /oclaims forceload for chunks that must stay loaded while you are online. You have 10.
Use /oclaims about to check how many claims and forceloads you have left.

Make a team and claim as a team#

Create a party with /ftbteams party create <name> or /oparties create [teamname] and invite at least one other player.
Run /teamclaims create <name> to make the team.
Select the team sub-config, named team_<name>. Claims made while it is selected are team claims. /oclaims sub-claim use <sub-id> chooses it.
Check the numbers with /teamclaims info, and the list with /teamclaims list.
To move existing claims, run /teamclaims convert toteam [radius] or topersonal [radius].

By default every member can make, unclaim and forceload team claims. The owner and admins can restrict each of the three actions to a minimum rank with /teamclaims roles. When a member leaves, their team claims go to the party owner.

Player commands#

Command	What it does
`/oclaims claim`, `unclaim`, `forceload`, `unforceload`	Claim, free or forceload chunks, with optional area arguments
`/oclaims about`	Show your numbers
`/oclaims sub-claim use <sub-id>` / `current`	Choose or show the claim sub-config
`/oclaims transfer ...`	Hand claims to someone else
`/oclaims clear confirm`	Remove all your claims
`/oparties create [teamname]`, `about`, `join <id>`, `leave`	Manage your OPAC party
`/oparties member invite <player>`, `member kick <name>`, `member rank <name> <rank>`	Invite and kick need moderator rank; ranks need admin
`/oparties ally add <player>`, `ally remove <owner>`	Allies
`/oparties transfer <new-owner> confirm`, `destroy confirm`, `chat <message>`	Hand over, delete, or chat (`/opm` is the short form)
`/opac get`, `set`, `sub create\|delete\|list`	Read and change your own claim settings
`/teamclaims create <name>`, `info`, `list [page]`, `roles`, `convert`, `territorymessages [on\|off]`	Team Claims

The permission requirements of a few /oclaims and /opac sub-commands were not read from the mod. The table lists the ones whose registration has no operator check.

Tips#

Claim before you build a farm or chest room. Hostile and friendly spawns still happen inside claims, so light the area up.
Use team claims for a shared base so nobody spends their private 500 chunks on it.
If a member leaves, the team's limit shrinks. A team that ends up above the new limit has 7 days to unclaim land or recruit before the newest team claims are released.
Do not rely on a claim to stop PvP. Combat between players is allowed inside claims by default.
Personal forceloads and team forceloads only work while their owner or a team member is online.
Lootr containers inside your claim are still per-player loot. See Per-Player Loot.
Admin tools (/oclaims admin-mode, moderator-mode, impersonate, teleport) are for staff ranks on a server. See Running a Server.

Changed from the old wiki#

Earlier versions of this wiki said that claims use FTB Chunks. In the current pack there is no FTB Chunks. They also said that OPAC parties are separate from FTB Teams. In the current pack, Team Claims 1.3.0 syncs the two. Finally, they said that every team claim counts against every member's limit and the smallest limit caps the team. In the current pack, a team has its own pool of 500 claims plus 25 per additional member.