Skip to main content

Using TDClaim

Mod version shipped with FlammiCraft: 4.30.0

TDClaim protects regions at every world height. Current operators manage claims; being recorded as their creator grants no permission by itself. Install compatible client and server builds. This guide describes the current Minecraft 1.21.1 source, with gameplay acceptance remaining a separate release check.

Requirements and upgrade

TDLibrary 0.74.0 or newer, including LDLib2, is required. Open Parties and Claims (openpartiesandclaims) and FTB Teams (ftbteams) are incompatible. OpenPAC integration is removed. Preserve external claims and decide their replacement before a manual switch; TDClaim neither imports nor deletes them. Inventory transfers retain live protection checks.

Create a claim

Install TDClaim 4.30.0 and TDLibrary 0.74.0 or newer on both server and clients, plus LDLib2 on both sides. The test server runs NeoForge 21.1.256 and LDLib2 2.2.46.a. See the installation reference for compatibility and update steps. See database and cluster setup for shared storage.

  1. Run /tdclaim as an operator and open Create claim.
  2. Obtain the Surveyor's Staff from the interface. The default is tdclaim:claim_tool; an existing server configuration may select another item.
  3. With the tool in your main hand, left-click corner one and right-click corner two in the same dimension. Both corner blocks are included on all three axes. Floors can share the same footprint when their Y ranges are disjoint.
  4. Return to the interface, for example with sneak-right-click while holding the tool. Enter a name and create the region.
  5. Select it under Claims and explicitly grant the intended player and group permissions.

Use Full world height in the claim overview to extend a bounded claim up and down without selecting new corners. The footprint stays the same. TDClaim rejects the change if the expanded claim would overlap another claim. Existing claims without stored height limits retain the full world height after upgrading.

A selection is a preview; creation is confirmed by the saved entry. Claims cannot overlap or touch more than 4096 chunks. Shrinking a claim removes block rules outside its new bounds.

Names and claim searches accept up to 64 characters; the dimension filter accepts 128. If an entry is too long, submitting shows which field to shorten. Your draft remains available, including after closing and reopening the interface.

Grant and inspect access

Public settings are the baseline. Personal overrides take precedence over group rules, and a denial from another group wins at the same rule level. Inherit removes one override, while Reset removes all overrides for the selected subject. Review bulk allow/deny confirmations.

The group editor switches between TDGroup player groups and TDEconomy businesses. Identically named groups remain independent. A TDGroupe assignment may target the whole group or its owner, manager or member role. An explicit role decision replaces the general group rule for that action; an inherited role falls back to it. Pending invitations grant no access.

Use Inspect & manage → Inspector, select a player and the relevant position, and read the deciding rule. This reports TDClaim's decision rather than another mod's authorization.

Claim borders require an active personal or group permission. Retired shop and account-terminal rights alone do not enable borders; their stored overrides remain intact.

Buy property

Property sales are off by default. Set claimSalesEnabled = true in tdclaim-server.toml and run TDEconomy 2.62.0 or newer with storage = "DATABASE". Use compatible server and client builds.

  1. As an operator, take a Claim Purchase Sign from Tools & Utilities in the creative inventory and place it inside the claim. Normal building permissions apply.
  2. Ctrl+right-click the sign. Choose a known player's account, a group account or a finite system account to receive the full price. A known player can be offline. Enter a positive price in Flammtaler with up to two decimal places and select the access permissions you want to sell.
  3. Activate the offer. A green sign is available and a gold sign is processing a payment. Deactivate a listing in the editor before breaking its sign.
  4. To buy, right-click the sign and review the claim name, price and permissions. The price uses TDEconomy's currency symbol. One Flammtaler equals 100 Funken. Buy charges your personal account. The sign disappears once the payment and purchased access have been saved.

New offers transfer claim ownership to the individual buyer after payment. The configured use rights belong to that player's UUID. Operators manage additional access and claim boundaries. Existing access-only listings retain their original terms. Revoke purchased access in the overview applies to those legacy grants.

A pending payment reserves the offer. After a restart or database outage, TDClaim checks the existing purchase ID. A conflicting receipt keeps the offer locked and logs the purchase ID. In database mode, the result is available in the TDLibrary inbox after switching backends or signing back in. See database and cluster setup for backups and recovery.

Rent homes and shops

TDClaim and TDEconomy 2.62.0 or newer require database mode for rentals. Upgrade every TDEconomy backend that can hold player account leases before activating rental offers.

  1. Place a Claim Rental Sign inside the claim within reach of its entrance. Ctrl+right-click as an operator. Choose the payout account type, enter its exact name and the weekly price in Flammtaler, and select the personal permissions to grant.
  2. Use the same offer group on related signs. The first offer with free days sets the shared trial duration. Set an offer to zero free days to charge immediately. Each player can use a group's free period once across the cluster. Paying for an immediate-charge offer leaves the trial available.
  3. Right-click the sign to start an eligible free period or confirm payment for one to four weeks. An existing tenant can add weeks to the covered period at the sign. The next charge appears in the sign screen. A reminder arrives in the TDLibrary inbox 24 hours before it is due.

The sign shows the current tenant and, during inventory review, the former tenant. Operators manage additional permissions. Changes to access rules made during a lease expire with it. Set permanent rules before the lease begins.

Confirmed insufficient funds end the lease. TDClaim revokes rental access and clears the former tenant's bed spawn if it belongs to that exact 3D claim. An unresolved payment keeps the claim reserved while its receipt is checked.

During Inventory review, the former tenant can pay for a new contract at the same sign without operator approval. A used trial stays used. An operator can review the reported location or choose Start clearing to lock out re-renting and remove items in admin mode. Release as empty verifies the contents again. Release with contents leaves the items for the next tenant.

An empty claim returns to the market as soon as the review verifies its contents. Automatic review covers up to 64 loaded chunks. Unloaded chunks, unknown mod storage, and containers spanning a boundary keep the claim under review. The check repeats as the data become available. Review larger or unverified areas manually before releasing them.

Block rules and automation

Choose Block permissions → Add the block you are looking at, or run /tdclaim blockpermission while aiming at it. The block must be loaded and within six blocks. An exception matches its exact position and registry type; another type cannot reuse it.

Transfers crossing to wilderness require an Automation boundary port at the claimed endpoint. Existing machines are not automatically opened by an update. Add the endpoint in the block editor and deliberately permit Automation Transfer. Transfers between different claims remain blocked even with ports at both ends. A port cannot identify who feeds an exposed outer network; wireless and mod-internal transports need their own integration.

Moving Create contraptions and trains have a deliberate exception. Stationary machines retain normal protection; moving machinery is not covered by a general cross-boundary protection guarantee.

A Create packager may serve a Create Stock Bridge inside the same region without a port. Across a claim boundary, it needs the same valid port as other automation; otherwise the bridge receives no orders.

A piston inside its own claim may push blocks into wilderness. Pistons outside a claim cannot move its blocks, and movements into another claim or protected spawn remain blocked.

Loading, spawn and administration

Configure force-loaded rectangles in the claim interface. Their union must fit maxForceLoadedChunksPerClaim. Lowering the limit removes tickets from oversized claims while retaining their saved areas.

With the server setting forceLoadRequiresOnlineMember = true, a claim's areas stay loaded only while one of its members is online. A member is a player with at least one explicit allow in the claim, personally or through a group. Public permissions and the operator who created the claim do not count. After the last member leaves, the claim stays loaded for forceLoadOfflineGraceMinutes minutes (default 10). After a server start without members it loads once a member joins. If a group membership cannot be determined, the claim stays loaded. The setting applies within a second without a restart; the default false keeps areas loaded around the clock as before. Machines and farms in a suspended claim stand still until a member is online again. Set forceLoadUsesClusterPresence = true to count members on other backends.

/tdclaim adminmode on enables an explicit operator bypass; use off to end it and status to inspect it. It is session-only and does not disable fixed environmental protection.

Use Spawn rules for the Overworld spawn and Dimension spawns for dimension-specific points. An explicit Overworld dimension spawn replaces its general configured spawn radii. Claim History can undo matching configuration changes, but cannot restore removed world blocks.

Every player with Xaero's World Map sees the effective spawn protection of each dimension on the world map and minimap, independent of the Claims map toggle. Touched chunks are drawn in yellow, and the tooltip shows the exact block bounds. See the reference for details.

Configuration and troubleshooting

World-local server settings live in serverconfig/tdclaim-server.toml; display settings live in config/tdclaim-client.toml. Apply server-file edits with /tdclaim reload, rather than vanilla /reload. The common debugSingleplayer startup option requires reopening the world. directSameRegionCapabilities (default true) lets connections inside one region skip TDClaim's guard and only changes on server restart.

Symptom Check
Right-clicking a block fails with NoClassDefFoundError in ItemMutationClassifier or invalid dist DEDICATED_SERVER in the same stack trace Update the server and clients to TDClaim 4.25.0. Repeat the click with the affected item in-game and verify that the configured claim permission allows or denies it.
Creator cannot use a block Inspect personal and group permissions; creator metadata grants no rights.
Internal transfer works, boundary transfer fails Check the endpoint, stored block type and automation port.
Borders are missing Check the inventory toggle, authorization, dimension and both display ranges.
Administration times out Refresh and inspect actual server state before repeating a mutation.
Persisted claims are rejected Stop the server and recover verified world and claim-data backups; do not clear the file.

See the detailed reference for the remaining protection, administration and configuration rules.