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.

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

How it works

1. Create a party — get a team

Create a party with a name in a single command:

/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. One fair, shared budget

Team claims are not free extra land. Every team claim counts against the claim limit of every party member, and a new team claim (or team forceload) is only accepted if all members still have room for it. In practice:

• Your claim counter shows your personal claims + all team claims of your party — in chat, in the claim UI and on the map.
• A party cannot out-claim solo players by stacking members: the member with the smallest limit caps the team.
• Server owners keep full control with the normal OPAC limits, bonus claims and permission-based limits.
• When a teammate is at their limit you get a clear message naming who is blocking the claim.

5. 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.

6. 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.

7. 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. If the whole party is disbanded, the team data is cleaned up.

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

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 1.0.0 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 and toteam has to fit into the shared team budget, 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
• Shared claim budget with per-member limit checks for claims and forceloads
• 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)
• Corrupt team files are kept as .corrupt-<timestamp> instead of being overwritten
• All player-facing messages are translatable; 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 44 automated server-side game tests 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.
   • 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 shared budget are gone in stock OPAC either way. Back up the world first, and keep team names short if you plan to go back.

Upgrading from 1.0.0

• Your world data loads unchanged: claims, parties and team configs from 1.0.0 are used as they are.
• Update the server and every client together. A 1.0.0 client with a 1.1.0 server is not a supported mix.
• On the first start the new server config is created. Its defaults keep the 1.0.0 behaviour (no grace period, every member may claim, unclaim and forceload), except that the claim welcome messages are now 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). Limits still come from your existing maxPlayerClaims / maxPlayerClaimForceloads, bonus options and permission systems.

• OPAC's own, separate partyOwnedClaims option can stay off. If you enable it as well, both systems share one claim pool per party owner; 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.

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.

Can I still have private claims? Yes. Only claims made while the team sub-config is selected are team claims, and personal claims are never restricted by team roles.

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 everyone's budget.

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

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.

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

This project is a fork of Open Parties and Claims by Xaero96 (CurseForge Project ID: 636608), redistributed under that mod's own license, the GNU LGPL v3.0.

It contains the complete Open Parties and Claims mod (version 0.31.6) with the Team Claims features built in. That is why it replaces the original jar instead of being installed next to it: both use the mod id openpartiesandclaims.

All credit for the original claim, party, protection, forceloading, configuration, API and map integration functionality goes to Xaero96 and the Open Parties and Claims contributors. Please support the original project.

This is an unofficial fork. It is not made, endorsed or supported by Xaero96, so please report problems with this build to its own issue tracker, not to the original project.

Original project:
https://www.curseforge.com/minecraft/mc-mods/open-parties-and-claims

Original author: Xaero96
CurseForge Project ID: 636608

License, source and issues

Licensed under the GNU LGPL v3.0 (LGPL-3.0-only), the same license as Open Parties and Claims.

Source code: https://github.com/navrelis/OPAC_PartyClaims
Issue tracker: https://github.com/navrelis/OPAC_PartyClaims/issues