Zum Hauptinhalt springen

TDClaim protection and administration reference

Mit FlammiCraft ausgelieferte Mod-Version: 4.30.0

Diese Detailseite ist derzeit auf Englisch verfügbar.

Handbook overview

Singleplayer testing

TDClaim is disabled by default in singleplayer, including worlds opened to LAN. Claims and saved protection data are not loaded or changed, and TDClaim does not apply protection, selection tools or force loading. Commands and client controls are inactive. Dedicated multiplayer servers remain enabled.

For testing, set the following in config/tdclaim-common.toml (created automatically on launch), then close and reopen the world:

debugSingleplayer = true

The default is false. This startup option is independent of /tdclaim reload.

Force loading

Operators can open Force loading for the selected claim and add multiple rectangular areas with the normal two-corner selection. Every area must be inside that claim. Together the areas may cover at most maxForceLoadedChunksPerClaim distinct chunks per claim; the default is 256 and the supported range is 1 through 4,096. Chunks shared by overlapping areas count once. Up to 4,096 rectangles can be stored, matching the existing maximum claim size. Only chunks touched by these areas receive full NeoForge chunk ticks, even when no players are nearby or online. Individual areas can be removed, and the editor shows current usage and the server limit. The areas survive server restarts; resizing a claim removes areas that no longer fit, while deletion and history operations update tickets automatically. Other chunk loaders keep their own tickets.

This keeps ticking machinery such as Mekanism, AE2, and Create active while the server is running. Keep all required machines, cables, storage, and moving machinery within the selected chunks. Force loading covers whole chunks, including blocks outside the exact area boundary in those chunks; it does not grant additional building or automation permissions. It cannot advance a stopped or paused server, and mechanics that explicitly require a player retain that requirement. Loaded factories continue consuming server resources while their owners are offline.

Installation

  1. Stop the server and back up the world, including world/data/tdclaim_claims.dat, before updates or manual data work.
  2. Place tdclaim-4.30.0.jar and TDLibrary 0.74.0 or newer in the server's mods folder and in the mods folder of every client. Replace older copies of each mod.
  3. Install LDLib2 on every client. The declared range is [2.2.37,). The test server runs 2.2.46.a. Xaero's World Map 1.45.0 or newer and Xaero's Minimap 26.4.2 or newer are optional.
  4. Start Minecraft 1.21.1 with NeoForge 21.1.256, the build and automated-test target for this release. The declared loader minimum remains 21.1.250; this does not imply a fresh test of older permitted versions.
  5. Adjust world/serverconfig/tdclaim-server.toml and config/tdclaim-client.toml if required. Server configuration can be applied during play with /tdclaim reload. Server and clients must use compatible TDClaim builds with protocol 20.

TDClaim has no hard dependency on TDEconomy. Open Parties and Claims and FTB Teams are incompatible. Xaero's Minimap 26.4.2 or newer is supported as an optional client dependency for the spawn waypoint. Xaero's World Map 1.45.0 or newer is an optional client dependency for the claim-map and spawn-protection overlays. FTB Chunks is not supported as a parallel claim system.

Player claim borders

Only active personal or group permissions qualify a player for claim borders. Retired shop and account-terminal overrides remain stored for compatibility but do not qualify, even if they allow access in old data. Public permissions alone do not qualify.

Active admin mode respects the saved inventory toggle: when enabled, it displays all nearby claim borders without requiring the selection tool; when disabled, borders remain hidden. Distance and loaded-terrain limits still apply.

The small clipboard-and-pen button controls nearby borders. With FTB Library installed, it appears in FTB Library's inventory sidebar, where players can arrange the buttons. Otherwise it sits above the upper-right edge of the survival and creative inventory. The standalone button draws only the icon, without a button background or status bar; it dims when switched off and grows slightly on hover or keyboard focus. Clicking the button toggles the display. The choice starts enabled and is saved per player UUID in the world's data/tdclaim_claims.dat. It is restored on joining, survives normal server restarts, and is independent for each world or server. Existing client-config choices are not imported. Update both server and clients to 3.7.0 for the new preference synchronization. Players see claims where a personal or active TDEconomy group rule grants at least one effective claim permission. Public permissions alone and recorded creator status do not qualify; personal and group denials retain their normal precedence.

The server searches the nearby claim index and sends only permitted claims in the current dimension, within the client render range and server limits (96 blocks by default). The client clips borders to its view distance, skips unloaded terrain, and draws only segments inside the camera view. This display never loads additional world chunks or downloads distant claim snapshots. Access is rechecked every two seconds while enabled. The inventory toggle controls visibility in admin mode as well: off hides borders, and on shows all nearby claims while admin mode is active. With borders enabled, operators can also inspect all nearby claims using the administration screen or selection tool. Leaving admin mode restores normal access filtering when neither inspection view is active. The separate operator-only Xaero claim map retains its existing behavior.

Without FTB Library, modpack authors can position the standalone button using these entries in config/tdclaim-client.toml (ship this client config with the pack):

claimButtonOffsetX = 0
claimButtonOffsetY = 0

Offsets are measured in GUI pixels relative to the default button position above the upper-right inventory edge. If there is not enough room above the inventory, the button aligns with the top of the screen. Positive X moves right, negative X left; positive Y moves down, negative Y up. For example, X = -8 and Y = 4 moves it eight GUI pixels left and four down. Both settings accept -4096 through 4096. GUI scaling applies to these pixels, and the button continues to follow the inventory. Edit the file with the client closed, then restart to apply it reliably.

Player groups and business groups

Claims can grant rights to both TDGroup player groups (provided by TDGroupe 0.13.0 or newer) and TDEconomy business groups at the same time. Both integrations are optional. In the group editor, the system button switches the displayed group list between TDGroup: player groups and TDEconomy: businesses. TDGroup is selected initially. The same switch is available when editing group rules for an individual block, including protected spawn blocks. Switching lists does not remove or change any permissions.

Each assignment stores its provider and group UUID, so identical names or UUIDs never share permissions across systems. Existing assignments without a provider remain TDEconomy business assignments. TDGroup grants follow accepted membership, including offline members; invitations alone grant no rights. TDEconomy grants retain the business account's existing mayUse checks. Leaving, removal and group deletion take effect in subsequent permission decisions.

The existing permission order applies across both providers: personal overrides take precedence, and a group denial wins over a group allowance at the same rule level. An unreadable installed provider denies only decisions governed by its rules; the other provider's independent rules remain usable. Server and clients must be updated together for network protocol 19. Group subjects use saved-data schema 15; older assignments load automatically with their original provider meaning.

Administration UI and claim tool

Names and claim searches accept up to 64 characters, and dimension filters up to 128. Submitting longer text shows which field to shorten without sending the action. Drafts survive closing and reopening the interface; searches preserve their entered case while matching without case sensitivity.

Current operators open the complete LDLib2 administration UI with /tdclaim. TDClaim deliberately registers no key binding. Its dark petrol, gold-accented presentation follows the same visual language as TDEconomy and separates the workflow into four primary tabs:

  • Create claim contains the selection tool, selection controls, and the new claim name. Creating a claim opens it in Claims.
  • Claims keeps claim discovery and editing in one compact dashboard. The selected claim directly lists its player and group overrides with their access states. Public, player, and group rule editors open as contextual views with a single Back action instead of adding a second tab bar.
  • Spawn rules shows the current Overworld spawn center, protection and mob-free radii, and every fixed protection rule. Conditional exceptions for verified shops, doors, waystones, seating, and rideable entities are clearly distinguished from fully allowed and blocked actions.
  • Dimension spawns uses a compact previous/next selector for configured dimensions and shows all editable protection rules for the selected spawn. Operators can cycle every rule between Default, Allow, and Deny, set or move the current dimension's spawn to their position, edit both radii, and remove a selected dimension spawn without leaving the UI.

The administration panel and confirmation dialogs automatically scale down as a whole when the current GUI scale or window size leaves too little space. Controls keep their layout and matching click areas; no particular Minecraft GUI scale is required. Resizing the window recalculates the fit without changing your GUI-scale setting. The UI starts on Claims after login, then remembers the open tab and subview, selected claim and targets, scroll positions, and local drafts when closed and reopened during that connection. Tool reports refresh from the server on reopening.

Data refreshes preserve the scroll position in claim and block lists, permission editors, spawn rules, and tool reports. If a list becomes shorter, its position is limited to the new end of the list.

Pending requests show a loading message. If a response times out, the UI reports that the outcome is unconfirmed and offers Refresh to check the server state. Reports distinguish loading, failed requests, and empty results; block searches without matches suggest clearing the filter. Claim titles use readable text beside a separate claim-color swatch. Spawn-rule help stays outside the scrolling list, and the single Tools entry opens visibly marked tool tabs.

Unsaved names, filters, and spawn radii survive refreshes and navigation, with claim names and radii kept separately for each target. Incoming updates preserve text focus, cursor position, and selection. Automatic refresh pauses while any text field is focused and uses the applied search filters. Reloading a report keeps the selected history entry or template where it still exists. Responses received during a confirmation update the underlying administration view; a changed target cancels the confirmation.

Operators can run /tdclaim debug chunks to open a separate LDLib2 chunk diagnostic screen. It lists Minecraft's tracked chunk holders across all dimensions, including pending loads, partial chunk data, and chunks awaiting unloading, independently of TDClaim claims. Filter by exact dimension ID, chunk or center coordinates, and ticket source (Minecraft spawn, players, TDClaim, other mods, or other vanilla tickets). Select a row to see the chunk center, current loading/ticking readiness, ticket origins and levels, force-tick flags, players located in or watching that chunk, and cached POI types and positions. Refresh captures a new server snapshot; page changes also capture current state, so a changing world can move rows between pages.

Direct tickets are distinguished from neighboring ticket influences calculated from Minecraft's propagated load levels. Multiple sources can overlap. NeoForge controller IDs identify their owning mod and block/UUID owner; custom tickets without such an ID expose their ticket type but cannot reliably identify the originating mod. The source filter includes neighboring influences, including partial generation dependencies. POIs are landmarks, not loading causes. Uncached POI sections are reported as unknown and are never loaded for the report. Snapshot queries do not add tickets, load chunks, or change claim settings. The details also list overlapping TDClaims, distinguishing whole-chunk coverage, partial coverage, and whether the center lies inside each claim. Claim coverage does not imply force loading.

The selected chunk has a Teleport to chunk button. The server rechecks operator permission, dimension, world border, and whether the target chunk is still fully loaded. It finds a clear standing position with solid ground at the chunk center, avoiding fluids and common hazardous ground; if none is found, the teleport is rejected. In dimensions with a ceiling, the search stays below the logical height. The UI closes when requesting a teleport and the server reports its result in chat. Normal player chunk loading applies after a successful teleport. Update the server and clients together for network protocol 19.

The Claims tab includes:

  • claim search, exact dimension filtering, paging, and distinct markers for the selected claim and the claim at the player's current position;
  • renaming, boundary replacement, and deletion for the selected claim;
  • public, player, and optional TDGroup player-group and TDEconomy business-group permissions;
  • a selectable player access list that combines the recorded creator, every player with a personal override, every online player, and every player with stored world data, marked online or offline and as full, blocked, custom, or public default;
  • an overview access summary with the creator, concrete player and group override names, access states, and the number of allowed public permissions;
  • bulk allow, bulk deny, and reset actions with contextual confirmations;
  • selection status, selection clearing, claim-tool delivery, and admin mode;
  • automatic nearby claim visualization while the UI is open or the selection tool is held.

All administration requests are bounded and revalidated against the current operator status on the server. The UI is never an authority source. Admin mode remains available through both the UI and its command. Other administration uses the UI, with a dedicated command for adding a targeted block permission entry.

The Claims map header toggle is visible only inside this operator-only UI. It sends every TDClaim claim to the authorized client in bounded batches and highlights the chunks touched by those claims in both Xaero's World Map and Xaero's Minimap. The overlay uses each claim's TDClaim color with fixed fill and border opacity; it does not use Xaero's OpenPAC visibility or opacity settings and does not require OpenPAC, FTB Chunks, FTB-Xaero-Compat, XaeroPlus, or World Map Bridge. Snapshots are limited to 262,144 expanded chunks to keep client-side work bounded. Turning the toggle off, losing operator status, changing dimension, or disconnecting clears the map snapshot and disables the server session.

Every player with Xaero's World Map also sees the effective spawn protection on the world map and minimap, independent of the Claims map toggle. The server sends the protected zone of each dimension that has one: dimension spawns and, for the Overworld, the configured spawnProtectionRadius around the world spawn the server adopted at start or the last /tdclaim reload. A radius of 0 shows nothing. Every chunk the square zone touches is filled and outlined in yellow; the tooltip names the zone, its exact block bounds as x min..max / z min..max, and any permissions a dimension spawn explicitly allows or blocks. While an operator's Claims map is on, chunks showing a claim keep the claim colors, because claims take precedence over spawn protection. Changes to the configuration or to dimension spawns update connected players immediately. Clients without this release keep working and simply do not show the overlay.

The default selection item is the non-craftable Surveyor's Staff (tdclaim:claim_tool). It is available in the Creative Tools and Utilities tab and through the UI. A configured registered item may replace it.

  • Left-click a block with the tool in the main hand to set corner 1.
  • Right-click a block with the tool in the main hand to set corner 2.
  • Shift-right-click with the tool in the main hand to open the administration UI without changing the selection.
  • Both corners must be in the same dimension.
  • Y coordinates are ignored; a claim applies at every height.
  • Claims may not overlap.
  • A claim may touch at most 4,096 chunks.

After both corners are set, create the claim in the UI. The client renders nearby claim borders as colored terrain-following ribbons. Each ground segment follows the highest loaded surface on both sides of the boundary and bridges height changes between its endpoints, keeping the border continuous across slopes, ledges, and ravines. Corner beams extend from the terrain past the viewer's current height. In addition, every claim side is drawn as one continuous textured curtain in the claim color that runs from corner to corner and from the world bottom to the build limit. Its texture scrolls upwards, so the boundary stays readable against terrain of a similar color and from far above or below. borderWallOpacity and borderScrollSpeed tune the effect, and showBorderWall = false keeps only the ground ribbons and corner beams. The server sends only authorized snapshots for the current dimension and configured range.

Permissions

Permission Protected action Public default
shop_use Legacy Econemy setting; TDEconomy now handles its own interactions allow
block_break Break blocks deny
block_place Place blocks and placeable entities; simple mode also controls the detailed construction actions deny
block_use Other block interactions; simple mode also controls doors, switches, beds and ordinary signs deny
container_use Open containers and machine inventories; Waystones use their own permission deny
item_drop Drop items inside the claim deny
hanging_entity_use Place, use, or remove item frames and paintings deny
entity_use Interact with animals, villagers, vehicles, and other entities deny
entity_damage Damage mobs and other non-player entities; shown as Mob damage in simple mode deny
pvp Both players must have this permission in the claim at the target's position for direct or indirect PvP damage; shown as Player damage in simple mode deny

Permission evaluation is deterministic:

  1. A current operator with active admin mode bypasses configurable player permissions.
  2. An explicit personal override applies.
  3. Active TDGroupe player-group and TDEconomy business-group overrides apply. A group deny wins over an allow from another group. Within one TDGroupe group, an explicit rule for the player's current role replaces that action's whole-group rule; inheritance falls back to the whole-group rule.
  4. The public claim setting applies.

Personal overrides therefore remain the precise final team decision for one player. createdBy is audit metadata only and never grants access.

Blocks registered by the Waystones mod are usable by default. Claims now have a dedicated waystone_use permission and matching block rules may override it. Their menus may expose an item-handler capability, but TDClaim recognizes the waystones namespace and applies waystone_use. This exception covers interaction only; it never grants permission to break, replace, or place blocks.

Travel through existing Nether, End, and custom-dimension portals does not require block_use. TDClaim does not cancel dimension changes based on permissions at the player's departure position, including protected spawn areas. Building or igniting portals and any required right-click block interactions still follow their normal permissions.

Detailed actions and block rules

The simple editor changes a category together with its detailed actions. The expert editor changes individual actions, including separate permissions for opening doors, fence gates, and trapdoors for public and player access. Existing saved door permissions migrate to all three actions. Opening or switching editors never changes permissions. A mixed category is marked custom, and replacing it requires confirmation. Missing personal or group detail overrides inherit that subject's broad action before normal group/public resolution.

Detailed actions are door_use, gate_use, trapdoor_use, switch_use, bed_use, sign_use, seat_use, waystone_use, tool_use, bucket_use, ignite, bonemeal, item_use_on_block, item_pickup, border_build, vehicle_use, leash_use, and shear_use. Seats, Waystones and item pickup are allowed by default; the other details inherit their original broad permission when older data is loaded. Entity lead/shear permissions identify the held tool, not every possible mod-specific outcome.

TDEconomy handles all interactions with its own blocks and interaction items, including cash registers, terminals, shop boards, multipart blocks and order clipboards. TDClaim delegates these actions without checking claim, player, group, block or spawn interaction overrides. The legacy shop_use and account_terminal_use values remain readable in saved data but do not restrict delegated TDEconomy interactions. They are omitted from permission editors, access summaries and current permission reports. TDEconomy remains responsible for account, business, shop and order authorization. Block placement, breaking, held building items, tools and automation still require their own claim permissions.

Open Block permissions from a selected claim and choose Add the block you are looking at, or run /tdclaim blockpermission "Shop A" while looking at a block in that claim. Repeating the command preserves the existing entry and its permissions. The server checks the operator, a six-block ray trace, dimension and claim bounds. New entries inherit everything. Select an entry and edit public, player or group rules in simple or expert mode. The entry stores the exact X/Y/Z position and registry block ID within its claim. State changes do not invalidate it. A different block type does not match; replacing it with the same type reactivates its rules. Removing the entry restores claim rules. Shrinking a claim removes entries outside the new bounds. Each claim supports 128 block entries and 128 block subject assignments in total.

At a matching block, personal rules take precedence, then group rules (deny wins), then public block rules, then the normal claim rules. Admin mode remains the explicit operator bypass. Block rules do not grant access to nearby blocks. A scanner may require both block interaction and Other item use for its card. Direct block mutations still need building/tool rights. TDClaim does not promise separate scanner configuration, inventory insertion/extraction or mod-network authorization without a verified integration. Shop-owned storage and shop administration remain governed by TDEconomy.

Block X-ray display

Operators can toggle Block X-ray from the selected claim or its block-permissions dialog. It draws translucent boxes with bright edges through walls around that claim's recorded block-rule positions, and remains visible after closing the UI. Green means at least one explicit allow is stored, blue means other or inherited rules, and orange means the current block type no longer matches. These colors describe stored rules, not one player's effective access.

Only loaded positions within the smaller server/client visualization range are drawn. The display is local to the viewing operator and does not change permissions. Switching claims or dimensions, deleting the claim or its last block entry, disconnecting, or losing operator authorization turns it off. While the UI is closed, the client refreshes the authorized claim snapshot every two seconds; absent fresh authorization, the display expires after ten seconds.

Boundary construction and automation

Claims may touch directly, including within the same chunk. The two-block environmental detection strip does not reserve land or extend either claim. Actions on a block inside a claim use that claim's player and block permissions; a touching shop does not add a second permission veto. On unclaimed land, the one-block exterior building border still requires border_build from every neighboring claim, including diagonal corners. Shop, seat or Waystone use alone never grants exterior building access.

Natural water/lava flow, fire and dispenser actions cannot enter a claim from wilderness or another claim. Internal environmental effects are allowed, including fire and non-mob explosions. A piston may operate internally, but cannot move or destroy another claim's blocks. Moving items, primed TNT and falling blocks are checked along their movement segment so they cannot skip a narrow claim in one tick. Explosions originating outside a claim cannot damage its blocks or entities or apply knockback, even when internal mob explosions are allowed. Primed TNT retains its original position across saving and loading; moving it into a claim does not make its explosion internal. Player actions and mob permissions are evaluated separately.

Technical item transfers, including hoppers and droppers, require an explicit Automation boundary port on the claimed endpoint when crossing to wilderness. The same rule protects standard sided NeoForge item, fluid and energy capabilities. Connections inside one claim, one spawn zone or between two unclaimed blocks receive the machine's own handler without a guard. Creating, resizing or deleting a claim, or changing a spawn zone, refreshes cached connections in the affected chunks; a cached connection that now crosses a border is guarded on its next use. A handler that a mod holds outside NeoForge's capability cache keeps its old state until that mod looks it up again. Set directSameRegionCapabilities = false to guard every sided connection; a guarded held handler revokes access immediately, including between two slots of one transfer. Permission edits do not invalidate internal geometry. Boundary port edits take effect immediately, and a port's actual loaded block type is checked before use. Crossings between different claims remain blocked even if both endpoints are ports or their player permissions are identical. Spawn boundary ports remain unavailable.

Create Liquid Fuel 3.0.0's internal Blaze Burner tank access is adapted to preserve Create's concrete tank type during ticking and container refilling. External sided fluid access remains guarded, including cached handlers after port revocation.

Create packagers recognize package request targets such as the Create Stock Bridge through TDClaim's item guard while the transfer is permitted. The decision is repeated on every lookup: without permission, the target stays hidden behind the guard and receives no orders.

A player with both claim-wide building and border-building permission automatically establishes a port when installing a block entity at the edge, or when building beside an existing edge block entity. This creates only the public AUTOMATION_TRANSFER override on that exact block position and registry type. Admins can inspect or revoke it in the block editor. An explicit denial is never overwritten by automatic placement. Replacing the block with the same type reactivates its stored rule; another type does not. Existing machinery is not automatically granted a port when upgrading or creating a claim around it: add its endpoint in the block editor and enable the port. Ports share the limit of 128 block rules per claim.

An open port is an intentional connection to wilderness, not proof of who supplied its contents. People may still feed or extend an exposed external network farther away. Unsided, wireless, direct inventory and mod-internal network paths need their own integration; the capability guard cannot infer an origin these APIs do not provide. See the FlammiCraft compatibility report for the inspected versions, covered paths and manual acceptance checks.

Inspecting and managing permissions

Open Inspect & manage in the claim UI:

  • Inspector: select a player and either the looked-at block within six blocks, a stored block entry, or claim rules without a block. The server resolves current player and group rules, inherited parent permissions, public defaults, explicit Admin mode and neighboring claim border denials. Results identify the deciding rule. Stored entries are checked against the actual loaded block type; the inspector does not load chunks. It reports TDClaim decisions, not permission guarantees from other mods. Entity-specific exemptions and hand-held item classification must still be checked with the corresponding action.
  • History: browse claim changes or all claims, including deleted ones. The last 256 changes are stored across restarts, with actor UUID/name, time, operation and complete before/after claim snapshots. This covers claim creation, deletion, renaming, bounds, public/player/group rights and block rules through both the UI and commands. Undo requires the current claim to match the recorded after-state and revalidates names and overlaps before restoring anything. Undo is itself recorded. It restores claim configuration, not world blocks. Dimension-spawn settings, template-library edits and session Admin-mode toggles are outside this claim history.
  • Templates: save up to 32 named permission templates, inspect their contents and apply them to another claim. Applying replaces public, player and group rules together, preserving the target claim identity, bounds and block exceptions. Saving over a name, applying and deleting require confirmation. Actual block positions are never transplanted by a template.

The block dialog supports text search by registry ID, localized name or coordinates. Copy permissions selects a source entry; Paste permissions replaces another selected entry's public/player/group rules while retaining its UUID, position and block type. Source permissions are read from the server at paste time. Copies and template applications appear in history.

SecurityCraft keycard readers and locks distinguish configured card/holder use (BLOCK_USE) from the configuration branch (CONTAINER_USE). Blank cards and codebreakers do not receive ordinary visitor use. SecurityCraft's own ownership and card checks still apply.

Create contraptions and trains are deliberately exempt. Their ticking, actor work and disassembly run in a scoped exception, including moving deployers and ploughs; the exception is removed even if Create throws. Stationary Create machines retain normal protection. Moving machinery may therefore modify blocks across claim boundaries. The optional adapter must be verified with the installed Create version and addons; it is not a protection guarantee for arbitrary remote mod operations.

Sophisticated Backpacks placed in the world require CONTAINER_USE at the backpack's location. Opening another player's worn backpack requires both the accessing player and the wearer to have CONTAINER_USE at the wearer's location. The server checks the worn-backpack opening packet as well. Sneaking to pick up a placed backpack requires BLOCK_BREAK. Players can still open their own inventory or worn backpack without claim access; Sophisticated Backpacks' own access settings continue to apply.

Player and group access

Select a player or an optional TDEconomy group in the claim UI to edit individual permissions, allow all, deny all, or reset overrides.

Group support is a read-only soft integration. When TDEconomy is present and compatible, TDClaim reads active group UUIDs, names, owners, and current membership. It never reads balances, transfers money, creates shops, sells claims, or treats a group as the claim owner. Missing, archived, or incompatible groups grant no access. Stored group overrides remain in TDClaim data so an unavailable integration never silently destroys configuration.

In the UI, operators select players from a list. It includes the recorded creator, players with existing overrides, players online anywhere in the cluster, known players from TDLibrary and local world profiles. The server sends at most 1,024 player choices and refreshes its directory cache about every 30 seconds.

Bulk allow and deny set all subject overrides. Reset removes all overrides for that player or group; Inherit removes only the selected override.

Commands

All /tdclaim commands require a current operator player, except reload, which is also available to the server console.

/tdclaim
/tdclaim adminmode <on|off|toggle|status>
/tdclaim blockpermission [claim]
/tdclaim reload
/tdclaim debug chunks

/tdclaim opens the administration UI. Use /tdclaim blockpermission to add the block under your crosshair to its claim or protected spawn's block-permission list, then edit its public, player or group rules in the UI. The region is resolved from the block's position, even when you stand outside it; an ordinary claim takes priority over the spawn. Optionally specify a claim with /tdclaim blockpermission "Shop A"; quote names containing spaces. The target must be within six blocks in a loaded chunk in the current dimension; an explicit claim name must match the target claim. Targets outside both claims and protected spawns are rejected. New entries inherit region permissions; existing entries keep their overrides.

/tdclaim reload reads the active TDClaim server TOML file, validates it, and applies it on the server thread. In the console, use tdclaim reload without the slash. NeoForge config reload events also update TDClaim automatically when its file watcher is enabled. Vanilla /reload reloads datapacks; use the TDClaim command for a deterministic configuration refresh. The new radii, current Overworld world-spawn center, selection tool, display ranges/colors, list size and denial cooldown become effective without replacing claims, block rules, dimension-spawn settings, selections or Admin-mode sessions. Existing mobs are not removed. spawnWaypointEnabled affects subsequent logins; it does not remove waypoints already saved by clients. If reading or validating the manual reload fails, the previous runtime settings remain active. NeoForge's own file watcher may separately correct invalid config values according to its normal validation rules.

Version 3.0.0 removes the former claim, selection, permission, player, group and dimension-spawn subcommands because these functions are available in the UI. Update any scripts using those commands. Existing claim data remains compatible. Boundary replacement in the UI preserves claim identity and permissions.

Admin mode

Admin mode is an explicit gameplay bypass, controlled by the UI header button or /tdclaim adminmode <on|off|toggle|status>. Enabling it in the UI requires confirmation. It is not persisted, starts disabled after login or server restart, is removed on logout, and only works while the player remains an operator. It does not disable fixed environmental protection.

Environmental protection

Friendly mobs (neither an Enemy nor in the MONSTER category), including villagers and allays, may pick up loose items inside claims by default. In the public expert editor, disable friendly_mob_pickup to block this. Both the mob and item locations are checked. Separately, enable friendly_mob_block_changes to allow block changes by non-hostile mobs, including snow golem snow trails and villager harvesting. This setting defaults to denied in new and migrated claims, and name tags do not bypass it. Hostile mob pickup stays blocked unless mob_griefing is allowed. These four mob settings apply to the whole claim, have no player/group/block overrides, and persist through restarts, history, and templates. They do not override vanilla mobGriefing=false or other mods. Spawn protection outside claims retains its fixed mob restrictions. Server and clients must update together for network protocol 19.

Every claim protects against the following by default:

  • incoming explosions, including block damage, entity damage and knockback; internal non-mob explosions are allowed, while internal mob explosions follow mob_explosions;
  • mob griefing and entity-driven block placement or destruction; public expert setting mob_griefing may allow hostile mob block changes, including Enderman block theft; friendly_mob_block_changes independently allows non-hostile mob block changes, including snow golem snow trails regardless of name tags;
  • incoming fire spread and burning, while internal fire is allowed;
  • pistons entering a claim or protected spawn or moving another region's blocks; a piston inside its own claim may push into wilderness;
  • fluid flow into claims or spawn protection from outside;
  • dispensers introducing content into claims or protected spawn from outside;
  • hopper and dropper transfers across claim boundaries without a matching technical port, and all such transfers between distinct claims or across spawn boundaries;
  • item entities moving between different claims or across spawn protection boundaries.

Explosions outside a claim continue to affect unclaimed positions while protected blocks and entities are removed from their effect.

Spawn protection

spawnProtectionRadius protects a square block radius around the Overworld spawn. A value of 0 disables it. Explicit TDClaims take precedence inside that area; uncovered spawn positions use the fixed spawn policy. Run /tdclaim reload after changing the config or using /setworldspawn to update the radius and center without restarting.

Open Block permissions on the Spawn protection or Dimension spawns page to add and edit spawn block entries. Public, player and group overrides, simple/expert editing, copying and removal work like claim block rules. Priority is block player, block group (deny wins between groups), block public, then the spawn-wide override or default policy. Each spawn supports 128 entries and 128 block subject assignments. Rules bind to exact X/Y/Z coordinates and the registry block ID; changing block state is allowed, while a different type does not match. Moving or shrinking a spawn retains its entries, but entries outside the current protection area have no effect. Removing a dimension spawn deletes its entries. Default-spawn entries are retained while an Overworld dimension spawn replaces that area and become applicable again when it is removed. The default-spawn page opens the currently effective Overworld spawn's block editor. Spawn block edits are outside claim history and templates; automation ports and environmental boundary exceptions remain unavailable for spawns.

Open Parties and Claims is incompatible. Its existing files are not imported, deleted or rewritten.

Mob-free spawn radius

mobFreeRadius defines a square block radius around the Overworld spawn, independent of spawnProtectionRadius. A value of 0 disables it. Run /tdclaim reload after changing the config or using /setworldspawn to update the radius and center without restarting.

Inside the radius:

  • hostile mob spawns are vetoed: natural spawns, spawners and trial spawners, structure and chunk-generation spawns, raids, patrols, jockeys, and spawn eggs, including those fired from dispensers;
  • mob-driven explosions, mob griefing, mob block placement or destruction, Enderman block theft, and snow golem snow trails are suppressed regardless of name tags;
  • /summon is exempt, so operators can still place display mobs.

The radius allows friendly mobs, including sheep, pigs, bred animals, golems, and chickens from thrown eggs. Hostile mobs are also checked when added to the world, including slime and magma cube split offspring and spawns that skip finalization. Village siege zombies are checked where they actually appear, so sieges outside the radius are not affected. Existing mobs loaded from disk remain unchanged; the radius does not remove mobs already present or stop them walking into the area. Player interaction restrictions are controlled separately by spawn protection.

Dimension spawns

A dimension spawn is an operator-managed protected point, one per dimension, set and edited through the administration UI. Use it to protect a public portal in the Nether or the End the way spawnProtectionRadius protects the Overworld spawn. It is a protection region only: it never moves players and never changes portal destinations or the vanilla spawn point.

Use the Dimension spawns tab to create or move a spawn to your current position, edit protection and mob-free radii, cycle permissions between Default/Allow/Deny, inspect configured spawns, or remove an entry. New spawns start with both radii at 64 blocks; moving an existing spawn preserves its radii. A radius of 0 disables the corresponding protection.

Inside the protection radius, every permission starts at default, which reproduces the Overworld spawn policy: item drops, active shop use, doors, Waystones, recognized modded seating blocks, and mounting horses, pigs, striders, camels, boats, and minecarts remain usable, while other configurable player actions are denied. Set a permission to allow to open that entire action or to deny to block it even when the built-in policy would exempt it. Seating recognition uses common furniture IDs and block tags such as chair, seat, stool, bench, sofa, couch, loveseat, and ottoman. The fixed environmental protections continue to apply, an explicit TDClaim inside the radius still takes precedence for player permissions within its own bounds.

Inside the mob-free radius, hostile mob spawns are vetoed and mob-driven explosions, griefing, Enderman block theft, and snow golem snow trails are suppressed outside explicit claims; claims use their public mob expert settings. Name tags do not bypass these restrictions. /summon is exempt. Friendly mobs may spawn. Hostile entities added without spawn finalization, including slime and magma cube split offspring, are blocked too. Existing entities loaded from disk are exempt.

Radius and permission changes take effect immediately. A dimension spawn overrides spawnProtectionRadius and mobFreeRadius for its dimension: once an Overworld dimension spawn exists, the two config options no longer apply to the Overworld. Dimension spawns and their permission overrides are stored with the claims for their world save.

TDEconomy compatibility

TDClaim 4.29.0 requires TDEconomy 2.62.0 or newer when TDEconomy is installed, and follows its corrected tdeconomy mod ID and Java packages. Update both mods on server and clients together. Stored business-group UUIDs and the historical ECONEMY permission-provider enum remain unchanged; existing claim grants retain their meaning. The old economy JAR cannot be loaded alongside the new one.

All blocks registered under tdeconomy are passed to TDEconomy for normal use, Shift-use and either hand, including newly added variants and multipart sections without block entities. TDClaim leaves the interaction event unchanged so TDEconomy and other event handlers retain their own decisions. Claims and protected spawns do not add a second interaction gate.

  • TDEconomy interaction items, including order clipboards, are also delegated; held blocks, buckets and tools retain their separate TDClaim checks.
  • Main-hand use of storage directly attached to an active shop board is passed to TDEconomy, which validates the stored shop owner and current group membership. Active attached-shop detection still requires tdeconomy:shop_sign and a positive numeric tdeconomy_shop marker.
  • This delegation grants no general container access, item drops, automation rights or neighboring-container access. A forged shop marker on an ordinary chest does not make it a shop.
  • TDEconomy handles its own shop owners, accounts and balances.

Claim Purchase Signs use the optional TDEconomy payment API starting at 2.52.0. Rentals require TDEconomy 2.62.0 or newer and database mode in both mods. See buy property and rent homes and shops for controls and recovery.

Configuration

Default server configuration in world/serverconfig/tdclaim-server.toml:

selectionTool = "tdclaim:claim_tool"
visualizationRange = 96
maxSynchronizedClaims = 256
maxForceLoadedChunksPerClaim = 256
listPageSize = 12
selectionColor = "#FFD700"
claimColorPalette = ["#00E5FF", "#FF4081", "#76FF03", "#E040FB", "#FF9100", "#40C4FF"]
deniedMessageCooldownTicks = 20
spawnProtectionRadius = 0
mobFreeRadius = 0
spawnWaypointEnabled = true
directSameRegionCapabilities = true

directSameRegionCapabilities lets item, fluid and energy connections within one region skip TDClaim's guard, which reduces server load from automation. It is read on server start; /tdclaim reload does not change it. Set it to false to guard every sided connection.

spawnWaypointEnabled sends every joining player a Xaero's Minimap waypoint named "Spawn" at the Overworld world spawn. The client needs Xaero's Minimap 26.4.2 or newer; without it the feature does nothing. An existing waypoint of the same name is reused and repositioned when the world spawn moves. Slow Xaero initialization and temporary waypoint-save failures are retried until the waypoint is durable or the player disconnects. Set the option to false to disable it.

maxForceLoadedChunksPerClaim limits the union of all force-loaded rectangles in one claim. Lowering it with /tdclaim reload immediately removes TDClaim tickets from claims that exceed the new limit without deleting their saved areas. Remove areas or raise the limit to activate those tickets again.

Existing server configs retain their saved selectionTool. Set it to tdclaim:claim_tool manually if an older config still uses minecraft:golden_hoe. Invalid or unregistered configured items produce a warning and use the golden hoe as a safe runtime fallback.

Default client configuration in config/tdclaim-client.toml:

autoShowWithSelectionTool = true
renderRange = 96
lineOpacity = 0.80
lineWidth = 0.28
beamOpacity = 0.28
beamHeight = 6.0
beamWidth = 0.20
showBorderWall = true
borderWallOpacity = 0.30
borderScrollSpeed = 1.5
showHighlightedClaimName = true

The effective render range is the smaller server/client value. Ground-line opacity accepts values from 0.65 to 1.0, and width accepts values from 0.20 to 0.5; older lower values are corrected when the client configuration is loaded. The boundary wall accepts an opacity from 0.02 to 1.0 and a scroll speed from 0.0 to 16.0 blocks per second; 0.0 keeps the texture static. Client configuration affects presentation only and never changes authorization.

Data and recovery

World storage uses world/data/tdclaim_claims.dat using schema 16. Schemas 1 through 15 migrate on load; friendly mob block changes default to denied; old door rules also initialize gate and trapdoor permissions. A legacy force-loaded claim becomes one force-loaded area; its tickets activate only while it fits the configured chunk limit. Older automation-port defaults remain denied; the account-terminal permission inherits the prior block-interaction setting. Stored data includes claim UUID, display name, dimension, X/Z bounds, creator UUID, force-loaded areas, public permissions, UUID-based player overrides, UUID-based TDEconomy group overrides, block rules, bounded claim history, named permission templates, per-dimension spawn points with their center and protection and mob-free radii, per-spawn permission overrides, and block rules for default and dimension spawns. See database and cluster setup for the dedicated-server database mode.

The spatial index, selections, admin mode, and notification cooldowns are rebuilt or cleared on every start. Corrupt, unknown, overlapping, or oversized persisted claims fail closed: the server does not silently replace them with an empty unprotected dataset. Stop the server and restore a verified backup before continuing.