Open Parties and Claims: Team Claims

Your party built the base together. Now your party can own it together.

This is a drop-in replacement build of Open Parties and Claims (OPAC) by Xaero96 for Fabric and NeoForge 1.21.1. It contains everything OPAC does — chunk claims, claim protection, forceloading, parties, allies, the full config UI, Xaero's Minimap / World Map integration, the complete API — and adds one thing OPAC players keep asking for: Team Claims.

The problem it solves

In stock OPAC every claim belongs to exactly one player. For a group that builds together this gets awkward fast:

• The base is claimed by whoever got there first. If that player is offline, nobody else can expand, unclaim or fix the borders.
• Forceloaded farms stop working when "the wrong person" logs off.
• Everyone has to configure their own claim color, name and permissions, so one base looks like a patchwork on the map.
• Giving the whole party access means fiddling with per-player protection settings, and one wrong toggle locks your friends out of their own storage room.
• Managing the party means typing /oparties ... commands, and if you also run FTB Teams, creating the same team twice.

Team Claims makes the party the unit that matters, while keeping every personal claim exactly as it was.

Updating from 1.1.0

Read this before you update a server. 1.2.0 splits the claim budget (see "Two separate budgets"). Your world data, claims, parties and team configs load unchanged, but:

• A team with a single member has a team claim limit of 0 with the default teamClaimsMinMembers = 2. When the 1.2.0 server starts, such a team is over its limit: its members get a warning (at their next login if they are offline), and after the grace period (overLimitGraceHours, 7 days of real time by default, also counted while the server is off) the newest team claims are unclaimed, until none are left. Team forceloads work the same way. A team of two or more members is only affected if it has more team claims or team forceloads than the new limits allow.
• The ways out: a second member joins the party, the members turn the team claims into private claims with /teamclaims convert topersonal (they have to fit into the players' own claim limit), they unclaim what they do not need, or you lower teamClaimsMinMembers (for example to 1) in openpartiesandclaims-teamclaims-server.toml.
• Update the server and every client together. The party screen and the budget numbers use new packets, so a 1.1.0 client with a 1.2.0 server (or the other way round) is not supported.
• The new options of the Team Claims server config are added with their defaults on the first start.

How it works

1. Create a party — get a team

Create a party with a name in a single command, or in the party screen:

/oparties create Iron Wolves

(or /teamclaims create Iron Wolves). The name is checked first (it must not be empty and may be at most 24 characters by default, see the server config below), then it becomes the party name, and every member — now and in the future — automatically receives a team sub-config called team_iron_wolves in their OPAC player config. Nobody has to set anything up. Existing parties are picked up automatically as well.

2. Claim for the team

Open the OPAC config (or use the usual OPAC sub-config option) and select the team sub-config as your active sub-config for new claims. From that moment, every chunk you claim — by command, keybind or by dragging on Xaero's World Map — is a team claim. Switch back to your main config whenever you want to claim something private. Personal and team claims live side by side.

Already claimed land with the wrong config? /teamclaims convert fixes it, see "Converting claims" below.

3. Everyone can manage team land

By default any party member can:

• unclaim a team claim, no matter which member originally claimed it,
• enable or disable forceloading on a team claim,
• build, break and interact everywhere on team land — party access on team claims is always on and cannot be switched off by accident.

No admin mode, no asking the original claimer to come online. If you want it stricter, see "Team roles".

4. Two separate budgets

Private claims and team claims do not compete:

• Private claims count against OPAC's own per-player limits (maxPlayerClaims, maxPlayerClaimForceloads, bonus options and permission-based limits) and nothing else. A team claim never uses one up.
• Team claims count against the team's pool only, whoever of the members made them. The pool depends on the number of members (the owner included, invited players not): a team below teamClaimsMinMembers (2) members has none, a team with exactly that many has teamClaimsBase (500) team claims and teamForceloadsBase (10) team forceloads, and every further member adds teamClaimsPerExtraMember (25) and teamForceloadsPerExtraMember (2). With the defaults: 2 members = 500 / 10, 3 = 525 / 12, 4 = 550 / 14.
• The claim counter in the claim UI and on the map shows the team's numbers while your team sub-config is selected, and your private numbers otherwise. /teamclaims info and the party screen show both.
• Server owners keep full control: the private limits stay OPAC's own, and the team pool is a handful of config options.

5. When a team is over its limit

A member leaves, you lower the limits, the update from 1.1.0 — a team can end up with more team claims (or team forceloads) than its limit allows. It is not punished at once:

• Every online member gets a chat message with the number over the limit, the time left (7 days by default, real time, also while the server is off) and the ways out; offline members get it at their next login, and everybody is reminded once a day. /teamclaims info and the party screen show the countdown. The team can make no new team claims meanwhile.
• If the team is back within its limit before the deadline — unclaim some, get more members, turn team claims into private claims with /teamclaims convert topersonal — the deadline is cancelled and nothing is removed.
• Otherwise the most recently made team claims are unclaimed, newest first, until the team is within its limit. For team forceloads the newest forceloads are turned off and the claims stay.

6. One look, one set of rules

A team claim should look and behave the same no matter who claimed it:

• The team gets a shared claim color (generated from the party, changeable) and a shared claim name.
• All protection options of the team sub-config are synchronized to every member automatically, including members who join later.
• Only the party owner and party admins can change team settings. For everyone else the options are shown read-only, and the server enforces it.
• The team sub-config cannot be deleted by hand — it disappears by itself when you leave the party.

7. Forceloading that follows the team

Forceloaded team chunks stay loaded while any party member is online, not just the player who flipped the switch. They behave like OPAC's own forceloads: random ticks and natural spawning work, and a dimension holding them keeps ticking without players. Your shared farms keep running when the claimer goes to bed and someone else is still playing.

When the last member logs off, the tickets are released — right away by default, or after a grace period the server owner can set (forceloadGraceMinutes). A member who comes back within that time cancels the release, so a short disconnect does not stop your farms.

8. Members come and go, the base stays

When a member leaves or is kicked, their team claims are transferred to the party owner automatically — including the forceload state — instead of turning into private land in the middle of your base. Both sides get a chat message. This also works if it happened while the server was offline. The team limit shrinks with the member count, so a team that is then over its limit gets the warning from section 5.

If the whole party is disbanded, its team claims become private claims of the members who made them, as far as each member's own claim limit allows; the rest is unclaimed at once, newest first, and forceloads are kept as far as the private forceload limit allows. Disbanding therefore never turns a team pool into extra private land. The disband confirmation says so.

Membership changes are handled as events and take effect in the same server tick, so even a quick join and leave is not missed.

Party screen

Press O (the default; rebindable in Controls under "Open Parties and Claims" as "Open Party Menu") or click Party in the OPAC menu. No more typing /oparties ...:

• Without a party: create one (the name is optional) and accept or decline the invitations sent to you.
• In a party: see the members and their ranks, invite players (online players are suggested), cancel invitations, kick, change ranks with one click, make someone the owner, rename the party, leave it, or disband it. Anything that needs a confirmation asks for it.
• The screen only offers what your rank allows, and every action runs the normal party command, so the server's checks and messages are the same.
• It shows your private claim and forceload numbers, and for a team the team numbers, a hint when the team is too small for team claims, and the countdown while the team is over its limit.

FTB Teams sync (optional)

Install FTB Teams next to this mod and your players only ever create one team. Parties and FTB Teams party teams are kept in sync in both directions; nothing of FTB Teams is bundled, and without it the mod works exactly as before. Tested with FTB Teams 2101.1.11.

• Synced: creating and disbanding a party, members joining, leaving and being kicked, the owner, the name, ranks (OPAC owner = FTB owner, OPAC admin and moderator = FTB officer, OPAC claimer and member = FTB member, an FTB officer becomes an OPAC moderator; an OPAC admin or claimer is not degraded) and invitations (an invitation in either mod exists in both, accepting it in either joins both).
• Not synced: allies, the FTB team colour, description and other properties, and party chat.
• OPAC wins on the first sync and wherever the mods disagree: a join, an invitation or a rename that OPAC cannot take is undone in FTB Teams and the player is told; an FTB party that is deleted while the OPAC party still has members FTB Teams does not know yet is created again.
• Disbanding in either mod disbands in both, and the team claims then follow the disband rule above.
• What cannot be synced yet (a player who has not logged in since FTB Teams was installed, a full FTB party (max_party_size), a change FTB Teams refuses, …) stays pending and is retried; the affected players are told, the log gets a warning, and /teamclaims ftbsync status lists it. FTB Teams has no events for invitations, declines and rank changes, so those are picked up within about a second.
• /teamclaims ftbsync status and /teamclaims ftbsync resync need permission level 2. The sync is controlled by the server option ftbTeamsSync (read at server start).

Commands

info and list only read, they change nothing.

Team roles

By default every member may make team claims, unclaim any team claim and toggle any team forceload. The party owner and admins can restrict each of these three actions to a minimum rank: member (the default), claimer, moderator, admin (OPAC's party ranks) or owner. A player below the rank is told which rank is needed, in chat for the claim commands and in the claim result on the map; nothing is changed. Claiming over a team claim of your own team with a personal sub-config takes it away from the team and so needs the unclaim rank. Personal claims are never restricted, and OPAC's admin mode and server claims ignore the roles. The roles are stored in the team config, and a team from an older version simply uses the defaults.

Converting claims

/teamclaims convert toteam [radius] is for land claimed before the team existed or with the wrong sub-config: every claim in the area that you own and that is not a team claim becomes a team claim, and topersonal does the opposite. The area is the square of chunks around the chunk you stand in (radius 0, the default, is only that chunk; at most convertMaxRadius, 4 by default). Only your own claims are touched, never a teammate's or another player's. Nothing is unclaimed in between and forceloads are kept. Every chunk goes through OPAC's normal claim rules: the team roles apply, toteam has to fit into the team pool and topersonal into your own claim limit, and the conversion stops at the first claim that does not fit. You get one summary: how many claims were converted, how many were skipped and why.

Territory messages

OPAC shows a line with the claim's name when you walk into a different claim. With Team Claims, moving from one claim of a team to another claim of the same team shows nothing, it is one territory. Entering or leaving a team's land, another team's land, a personal claim or the wilderness works as in OPAC. /teamclaims territorymessages off silences all claim welcome messages for you, not only the team ones; server owners choose what players who never used it get. This only applies while OPAC's own claimWelcomeMessages option is on.

Feature overview

• Automatic team_<party name> sub-config for every party member (long and non-ASCII party names supported)
• Team claims and personal claims side by side, switchable at any time
• Separate budgets: private claims against OPAC's own limits, team claims against a team pool that grows with the member count, for claims and forceloads
• Over-limit warning with a configurable grace period before the newest team claims are removed
• Party screen on the O key and in the OPAC menu
• Optional two-way sync with FTB Teams
• Team roles: choose the rank needed to claim, unclaim and forceload
• /teamclaims convert between personal and team claims in an area
• /teamclaims info and /teamclaims list for a team overview
• Teammates can unclaim and toggle forceload on team claims (by default)
• Party access permanently guaranteed on team claims
• Shared, synchronized claim color, claim name and protection settings, also for late joiners
• Owner/admin-only editing, enforced server-side, read-only UI for members
• Team forceloads active while any member is online, with an optional grace period, random ticks and natural spawning
• Team-aware claim welcome messages and a per-player switch
• Automatic claim transfer to the party owner on leave/kick (also after server downtime)
• Disbanding keeps team claims as private claims only within the owners' private limits
• Corrupt team files are kept as .corrupt-<timestamp> instead of being overwritten
• All player-facing messages are translatable (English and German included); players without the language file still get readable text
• Team data is stored per world, so singleplayer worlds never mix
• Fully compatible with Xaero's Minimap and Xaero's World Map claim display and claim controls
• Covered by 77 automated server-side game tests (111 with FTB Teams installed) that run on both loaders

Installation

1. Remove the original Open Parties and Claims jar. This mod is Open Parties and Claims (same mod id openpartiesandclaims) with Team Claims built in — the two cannot be installed together.
2. Download the file for your mod loader and put it into the mods folder of the server and every client.
3. Requirements:
   • Fabric: Minecraft 1.21.1, Fabric Loader 0.14 or newer, Fabric API, Forge Config API Port.
   • NeoForge: Minecraft 1.21.1, NeoForge 21.1.x. Nothing else is needed.
   • Optional: FTB Teams (with the FTB Library and Architectury it needs itself) for the party sync.
   • Recommended on both: Xaero's Minimap and Xaero's World Map.

Existing OPAC worlds, claims, parties and configs are used as they are.

Going back to stock OPAC: stock OPAC only accepts sub-config ids of up to 16 characters, and a team sub-config is called team_ plus the team name, so it fits only when the name takes at most 11 characters (team_iron_wolves is exactly 16; ids that had to be made unique with a suffix are longer). Those team sub-configs keep working in stock OPAC as ordinary sub-configs of the players. Stock OPAC does not load a longer team sub-config (its file is silently left unused), and the claims that used it become ordinary claims of the claimer's main config when stock loads them, with their forceload kept. Team sharing, roles and the team budget are gone in stock OPAC either way, and there all of a player's claims count against that player's own limit. Back up the world first, and keep team names short if you plan to go back.

Upgrading from 1.1.0

See "Updating from 1.1.0" at the top: single-member teams lose their team claims after the grace period unless a second member joins, they convert the claims, or you lower teamClaimsMinMembers. Update the server and every client together.

Upgrading from 1.0.0

• Your world data loads unchanged: claims, parties and team configs from 1.0.0 are used as they are. Read "Updating from 1.1.0" as well, the budget change applies to you too.
• Update the server and every client together.
• On the first start the new server config is created. The forceload grace period is off, every member may claim, unclaim and forceload, and the claim welcome messages are team-aware.

For server owners

• Based on Open Parties and Claims 0.31.6; every OPAC server option, permission node and command works as documented upstream.
• Team Claims has its own config, openpartiesandclaims-teamclaims-server.toml, next to OPAC's own (generated in the config folder at server start on both loaders; a copy in <world>/serverconfig/ overrides it for that world). The private limits still come from your existing maxPlayerClaims / maxPlayerClaimForceloads, bonus options and permission systems.

• Changes to the Team Claims config apply right away, except enabled and ftbTeamsSync (read at server start) and forceloadGraceMinutes (from the next logout). Teams are re-checked against their limits on every membership change and at least once a minute.
• OPAC's own, separate partyOwnedClaims option can stay off. If you enable it as well, native party claims count as private claims of the party owner (against the owner's own limit, which claimBonusPerPartyMember and claimBonusForPartyOwner raise) and never against the team's pool; the server log explains the details at startup.
• Team data lives in <world>/data/opacteamclaims/ and in the world's saved data.
• Mods built against the OPAC API (parties, claims, config API, addon events) keep working. getClaimCount() of a player still includes the team claims the player technically owns.

FAQ

Do clients need it? Yes. Like OPAC itself, it has to be installed on both sides for the UI, map integration and config screens.

Is FTB Teams required? No. It is an optional dependency: install it and the sync starts, leave it out and nothing changes. The mod is tested both ways.

Can I still have private claims? Yes. Only claims made while the team sub-config is selected are team claims. Private claims have their own limit and are never restricted by team roles; team claims do not use it up.

Who technically owns a team claim? The member who claimed it (so OPAC's data stays fully compatible), but the whole party can manage it and it counts for the team's pool.

What happens to team land when I leave the party? Your team claims move to the party owner. Your personal claims stay yours.

What happens to team land when the party is disbanded? Each team claim becomes a private claim of the member who made it, as far as that member's own claim limit allows; the rest is unclaimed.

Can I restrict who may claim or forceload for the team? Yes, the party owner or an admin sets a minimum rank per action with /teamclaims roles.

Does it work with other party systems (FTB Teams, Argonauts)? Team Claims is built on OPAC's default party system. FTB Teams parties are kept in sync with it (optional, see above); Argonauts is not synced.

Which versions and loaders are supported? Minecraft 1.21.1 on Fabric and on NeoForge 21.1.x. Forge and other Minecraft versions are not supported.

Credits & license

Open Parties and Claims is created by Xaero96 and contributors — all credit for the claim, party and protection systems goes to them. Please support the original project: https://www.curseforge.com/minecraft/mc-mods/open-parties-and-claims

Team Claims fork by Navrelis. Licensed under the GNU LGPL v3.0 (LGPL-3.0-only), the same license as the original. Source code: https://github.com/navrelis/OPAC_PartyClaims

Please report issues with this build to the fork's issue tracker (https://github.com/navrelis/OPAC_PartyClaims/issues), not to Xaero.