TDClaim Changelog

Mit BuildUp ausgelieferte Version: 4.5.0

4.5.0 · 4.4.0 · 4.3.0 · 4.2.0 · 4.1.2 · 4.1.1 · 4.1.0 · 4.0.1 · 4.0.0 · 3.12.8 · 3.12.7 · 3.12.6 · 3.12.5 · 3.12.4 · 3.12.3 · 3.12.2 · 3.12.1 · 3.12.0 · 3.11.1 · 3.11.0 · 3.10.0 · 3.9.1 · 3.9.0 · 3.8.1 · 3.8.0 · 3.7.0 · 3.6.3 · 3.6.2 · 3.6.1 · 3.6.0 · 3.5.1 · 3.5.0 · 3.4.5 · 3.4.4 · 3.4.3 · 3.4.2 · 3.4.1 · 3.4.0 · 3.3.0 · 3.2.3 · 3.2.2 · 3.2.1 · 3.2.0 · 3.1.0 · 3.0.3 · 3.0.2 · 3.0.1 · 3.0.0 · 2.10.0 · 2.9.0 · 2.8.0 · 2.7.0 · 2.6.1 · 2.6.0 · 2.5.2 · 2.5.1 · 2.5.0 · 2.4.0 · 2.3.0 · 2.2.3 · 2.2.2 · 2.2.1 · 2.2.0 · 2.1.1 · 2.1.0 · 2.0.0 · 1.1.5 · 1.1.4 · 1.1.2 · 1.1.1 · 1.1.0 · 1.0.1 · 1.0.0

4.5.0

• Provide a native plain item-insertion loop for TDLibrary 0.28.0's optional adapter. Recheck slot counts and permissions after every callback while reducing wrapper dispatch in automated item transfers. Simulation and denial behavior remain unchanged.

4.4.0

• Requires TDLibrary 0.19.0 or newer. Strict claim loading rejects a root data tag with the wrong NBT type. Network collection limits and the existing claim screen layout remain unchanged.

4.3.0

• Share claims with TDGroup player groups and TDEconemy business groups simultaneously. Add a group-system button to claim and block permission editors, initially selecting TDGroup; switching lists preserves existing grants. Track each group's provider separately, retain existing TDEconemy assignments, and apply current membership and the existing deny precedence across both systems. Update server and clients together for network protocol 17; group assignments use saved-data schema 14.

• Prevent hoppers and hopper minecarts from collecting loose items across protected boundaries, including the minecart's nearby-item fallback. Internal pickup and explicit automation ports retain their normal rules.

• Preserve existing Open Parties and Claims protection when TDClaims or protected spawns overlap part of its claimed chunks. Overlapping areas remain subject to both mods' restrictions.

• Correct full-trust and full-denial summaries for player and group permissions by excluding actions that cannot have personal or group overrides.

• Retain all claims sharing a map chunk, blend their colors and list every name in the tooltip. Reuse unchanged map snapshots after permission, block-rule and force-loading edits instead of retransmitting and rebuilding them.

• Avoid repeating the complete claim validation during each persistence encoding while retaining invalid-data rejection at both encoding entry points.

• Disable TDClaim in singleplayer by default, including LAN worlds: claims, spawn and mob protection, selection tools, force loading, commands and client controls remain inactive. Enable debugSingleplayer in config/tdclaim-common.toml and reopen the world to test all features. Dedicated servers remain enabled.

4.2.0

• Shorten the frequently executed automation-boundary check by separating border and port-rule refresh work from unchanged-region access. Every inventory operation still checks the current protection view and thread ownership; live port checks, immediate permission revocation and runtime replacement remain enforced.

4.1.2

• Immediately resynchronize the client inventory with the server after rejected block placement and item use, preventing temporarily missing items and ghost filled buckets.
• Correct inventory, affected blocks and interacted entities after denied player actions, including mod callbacks that return success or pass after a protected mutation was blocked. Multiple denials in one tick share a correction; correction reads never load missing chunks.
• Require bucket permission as well as entity interaction permission when collecting fish, axolotls, tadpoles and other bucketable mobs. Rejected pickup also restores the mob on the client.

4.1.1

• Keep cached boundary geometry when only dimension-spawn permissions change, while publishing the new permissions immediately. Moving, resizing or removing a protected spawn still invalidates boundary decisions.
• Avoid repeated position lookups when checking automation ports and short movements near claim borders. Loaded-block checks and immediate access revocation remain intact.

4.1.0

• Skip the moving-contraption scope lookup when a held automation capability already connects the same protection region. Every operation still checks thread ownership and the current protection snapshot; changed borders, port rules and revoked access remain visible immediately.

4.0.1

• Remove the obsolete shopSignMarker server setting and custom-marker shop recognition. TDEconemy shops continue to use their fixed block ID and persistent-data marker. Existing config files containing the removed setting remain readable during manual reload.

4.0.0

• Rebuild environmental protection around exact claim boundaries. Internal fire, non-mob explosions and automation are allowed; incoming effects from wilderness and neighboring claims are blocked. Player, mob and explicit block permissions remain independent.
• Separate claim geometry from permission updates and prepare chunk lookups on a worker without delaying protection. Claim bounds and force-load edits invalidate spatial state; ordinary permission changes no longer rebuild geometry or force-load plans.
• Remove thread-local protection-view lookups from server-thread automation and ordinary world-read guards while retaining stale-view rejection and immediate revocation of held machine connections.
• Protect against moving items and primed TNT crossing or skipping over narrow claims, including claims that share an edge without a gap.
• Exempt Create contraptions and trains from TDClaim protection. This intentionally permits their effects across claim boundaries.

3.12.8

• Avoid a duplicate protection-view lookup in each guarded automation operation while retaining thread checks, immediate protection revision updates and rejection of historical views.

3.12.7

• Reduce repeated item, fluid and energy transport protection work by reusing boundary decisions and matching automation port rules until claim or spawn protection changes. Held capabilities still observe same-tick permission revocation, block replacement, unavailable chunks and runtime shutdown, and retain server-thread enforcement.

3.12.6

• Prevent TDClaim mob-griefing and item-pickup permission checks from forcing Tessellate region ticking back to serial execution. Continue enforcing hostile and friendly mob permissions, target claim boundaries, and mob-free zones using consistent protection snapshots.

3.12.5

• Prevent tool item previews in Legendary Tooltips and EMI from triggering server-thread protection errors, while preserving permission checks for actual player tool use.

3.12.4

• Fix spawn-finalization errors during parallel chunk generation, including C2ME workers, while continuing to block hostile mobs inside mob-free zones.

3.12.3

• Keep current claim and spawn protection intact when an update is published inside a historical read of another protection store.
• Avoid reading TDEconemy group accounts for environmental damage and projectile impacts that do not require player permission checks.
• Publish claims, spatial lookups, spawn rules and configuration as consistent protection snapshots, so a multi-target decision cannot mix revisions.
• Keep cached item, fluid and energy capabilities protected when claim borders or automation permissions change.
• Capture all group memberships needed by a decision from one TDEconemy group-account snapshot and retain fail-closed handling when the provider is unavailable.
• Keep administration, audit attribution and chunk-ticket updates on their owner context while allowing detached protection data to be read in parallel.
• Preserve existing permission precedence, factory transfers and force-loaded areas without introducing Tessellate or region ticking.

3.12.2

• Reject force-load selections outside the selected claim or beyond the configured chunk limit before enumerating their chunks, preventing excessive memory use from large invalid selections.
• Send a small rejection for rate-limited administration requests without rebuilding claim details or refreshing visualization. Keep the client's last authorized editor state and acknowledge the rejected request.
• Show added and removed force-loaded rectangles in claim history so operators can review the affected areas before undoing a change.
• Deny actions governed by group rules when an installed TDEconemy integration cannot read membership, rather than silently falling back to public access. Preserve higher-priority personal permissions and explicit admin mode for claims and spawn block rules.
• Keep large access lists usable in the administration screen with bounded player and group pages and Previous/Next controls. Reject new assignments beyond 4,096 subjects per category before changing the claim, while retaining and allowing edits to larger existing lists. Do not present assignments on other pages as inherited permissions. Update the server and all clients together for network protocol 16.
• Resolve group names once per claim detail view instead of repeatedly reading and sorting all active groups for each comparison, reducing administration work on the server thread.
• Bound the client claim-border geometry cache to 512 entries and 65,536 line and beam segments, including entries created in the same game tick. Evict the least recently accessed geometry instead of repeatedly scanning the entire cache for old entries, limiting retained geometry during movement while preserving the existing game-tick freshness and render range.

3.12.1

• Apply the existing Econemy shop-use permission to TDEconemy's new daily quest signs, including claim and protected-spawn rules. Placement, breaking and held-item permissions remain separate.

3.12.0

• Add the public expert setting friendly_mob_block_changes to allow non-hostile mob block changes, including snow golem snow trails and villager harvesting, separately from Enderman block theft and other hostile mob changes. The new setting defaults to denied in new and existing claims. Snow golem name tags no longer bypass claim or spawn restrictions. Vanilla mobGriefing and other mods still apply. Store the setting in data schema 13, including history and templates; update the server and clients together for network protocol 15.
• Suppress protection feedback for automation actors and disconnected players while preserving every denied action. Create plough fake players no longer trigger client notification channel checks. Requires TDLibrary 0.6.0 or newer.

3.11.1

• Prevent protection checks from loading unloaded claim chunks or neighboring chunks during automatic boundary-port detection and shop-storage checks. Resolve block permissions from already loaded chunks in the target dimension, deny block operations whose protected target is unavailable, and avoid block lookups for entity and item permissions. Explicitly configured force-loaded areas retain their existing behavior.
• Keep TDClaim's extra piston-structure, container classification, and bucket, boat, and spawn-egg targeting checks within already loaded chunks. Cancel actions whose checks reach unavailable chunks instead of loading them, including block, fluid, and block-entity reads made by the checks. Spawn exceptions for doors, seats, and waystones also use loaded data in the target dimension. Hopper protection uses the hopper's cached state.
• Restrict placement-target calculation and the targeting rays used to add or inspect block rules to loaded chunks. Abort checks that reach unloaded data before their target validation can request chunks.

3.11.0

• Add an operator-only teleport button to the selected chunk's diagnostic details, with server-side permission, loaded-chunk, world-border, and safe-standing-position checks. Show overlapping claim names, whole or partial chunk coverage, and whether the chunk center lies inside each claim; claim coverage remains distinct from force loading.

• Add /tdclaim debug chunks for operators, opening a separate LDLib2 overview of Minecraft's tracked chunks across dimensions. Show chunk centers, pending and partial loads, chunks awaiting unloading, ticking readiness, direct and neighboring ticket influences, Minecraft spawn tickets, player tickets, TDClaim and other NeoForge controller owners, and cached POI positions. Add dimension, coordinate and source filters, paging, and manual refresh without loading additional chunks. Custom ticket providers without an exposed mod ID remain explicitly unattributed; uncached POI sections remain unknown. Update the server and clients together for network protocol 14.

3.10.0

• Let villagers, allays, and other non-hostile mobs pick up dropped items inside claims by default, without granting block-changing rights. Add public claim expert settings to disable friendly item pickup or allow mob block changes and mob explosions independently. Existing claims receive these defaults; vanilla mobGriefing and other mods still apply.

• Split opening doors, fence gates, and trapdoors into separate expert permissions for public and individual player access. Existing door permissions are preserved for all three actions when loading older saved data. Update the server and all clients together for network protocol 13.

• Route protection denials, selection hints, port-limit feedback and client operation messages through shared TD notification presentation. Preserve cooldowns and permission checks; frequent hints remain transient and do not fill persistent history.

• Require TDLibrary 0.1.0 for shared technical helpers; its runtime requires NeoForge 21.1.250 or newer.

• Use Unicode-safe bounded text for claim labels without splitting surrogate pairs; preserve request limits, notification cooldowns and permission checks through shared primitives.

3.9.1

• Protect placed Sophisticated Backpacks with container-use permission. Opening another player's worn backpack requires both players to have container-use permission at the wearer's location, including access through the opening packet. Picking up a placed backpack while sneaking requires block-break permission. Opening your own inventory or worn backpack remains available without claim access.

3.9.0

• Expand the existing shop permission into a single Econemy option for market boards and pillars, order boards and crates, both notice boards, quest signs, and all eight terminal and cash register variants. Check every clicked block part and let TDEconemy enforce its editing, clipboard, account, and order rights; building and held-item permissions remain separate. Existing shop rules also control terminal access; the old terminal option is retained only for saved-data compatibility.

3.8.1

• Restore offline players in the administration screen's player selection by loading the player cache on first access and clearing it when the server stops or changes.
• Reject saved data with missing dimension spawn records in schema 4 or newer instead of silently discarding configured spawn protection. Older schemas without dimension spawns remain supported.
• Let machines use their original item, fluid, and energy capabilities inside a single claim, avoiding TDClaim's transfer wrapper during normal operation. When a claim boundary changes, invalidate those capabilities so caching machines request the new boundary-protected handler.
• Close open editors such as public, player, group, or force-loading permissions when another claim is selected in the administration screen, so the new claim opens on its overview instead of an editor meant for the previous one.

3.8.0

• Let snow golems that carry a name tag leave snow trails inside claims and mob-free spawn areas. Unnamed snow golems remain blocked there, as before.
• Reduce server work for inventory, fluid, and energy connections whose ends both lie in the same claim or spawn area, or both outside every protected area. TDClaim now reuses that decision until a claim, dimension spawn, or boundary configuration changes instead of repeating the protection lookup every tick. Connections across a claim or spawn border, including automation boundary ports, are still rechecked every tick.
• Respect the inventory border toggle in admin mode, the administration screen, and while holding the selection tool. Turning it off hides borders; turning it on in admin mode shows all nearby claims, while ordinary players see only accessible claims.

3.7.0

• Store each player's claim-border toggle in the world's data/tdclaim_claims.dat, keyed by player UUID, and restore it when joining. The choice survives reconnects and normal server restarts and is independent for each world or server, even when switching client instances.
• Remove showAccessibleClaims from the client configuration. Existing client choices are not imported; players without a saved world preference start with borders enabled. Admin mode continues to show nearby borders regardless of this preference.
• Update the network protocol for preference synchronization; update TDClaim on both the server and clients together.

3.6.3

• Show a proper title for the claim-border button in FTB Library's sidebar tooltip instead of the raw sidebar_button.tdclaim.claim_borders translation key.

3.6.2

• Fix village sieges being blocked anywhere in the world when the mob-free spawn radius covers the world origin. Siege zombies are now checked at the position where they actually appear.

3.6.1

• Add the claim-border toggle to FTB Library's inventory sidebar when FTB Library is installed; otherwise keep TDClaim's button above the inventory.
• Keep the inventory claim toggle clear of JEI and EMI item lists at larger GUI scales by placing it above the upper-right inventory edge, or at the screen top when space is tight.
• Render the inventory claim toggle as just the clipboard icon, without the button background or status bar. The icon dims when switched off and grows slightly on hover or keyboard focus; clicking, keyboard activation, tooltips, and configurable positioning remain available.

3.6.0

• Place the claim-border button beside the lower-right inventory edge to avoid the existing mod-button column on the left.
• Add client configuration offsets for the claim-border button so modpack authors can adjust its horizontal and vertical position without changing the inventory layout. The icon, click area, and tooltip follow the configured position.

3.5.1

• Require both players to have PvP permission in the claim at the target's position. Players without permission are protected from authorized attackers, including projectiles and player-owned indirect damage; explicit admin mode still bypasses protection.
• Move the claim-border toggle from the screen corner to the lower-left inventory edge beside the hotbar. Use a compact clipboard-and-pen icon button with a state indicator and tooltip, and keep its position and click area aligned when the inventory moves or the GUI scale changes.

3.5.0

• Keep all nearby claim borders visible while server-authorized admin mode is active, even without the selection tool and with the inventory toggle off. Command and UI changes take effect immediately; leaving admin mode restores the normal border preference and access filtering.
• Add a saved, enabled-by-default claim-border toggle to survival and creative inventories. Players see nearby claims with an effective personal or group permission; public access alone does not reveal borders. Existing operator visualization remains available.
• Look up nearby claims through the chunk index, limit synchronization to the current dimension and viewing range, and skip border segments outside the camera view or in unloaded terrain without loading extra chunks.
• Update the network protocol for player border requests; update the server and clients together.

3.4.5

• Put claim creation in a top-level tab before Claims. Keep Claims as the first tab shown after login, remember the open tab and subview, selected claim and targets, scroll positions, and drafts when reopening during the same connection, refresh tool reports from the server, and open a newly created claim in Claims.

3.4.4

• Move claim creation into a separate view with its own name field and selection tools. Keep renaming and existing-claim actions in the selected claim overview to reduce accidental clicks.

3.4.3

• Label mob damage and player damage as separate permissions in the simple editor, making clear that either protection can be configured without changing the other.

3.4.2

• Stop re-reading both endpoint block states for every slot in a cached automation capability. NeoForge capability invalidation handles replaced endpoint blocks, while TDClaim revisions continue to invalidate claim and permission changes immediately.

3.4.1

• Reuse claim-boundary decisions and derived spawn-zone geometry while automation scans the same sided capability during a server tick, avoiding repeated claim, UUID and geometry work for every inventory slot while invalidating cached decisions when claims, permissions, dimension spawns, configuration, runtime, or endpoint block states change.

3.4.0

• Render every claim side as a continuous textured wall in the claim color, from corner to corner and from the world bottom to the build limit, instead of marking only the four corners. The texture scrolls upwards and is limited to the active render range. The new client options showBorderWall, borderWallOpacity, and borderScrollSpeed control the display.
• Add an operator-only administration toggle that displays every TDClaim claim in Xaero's World Map and Minimap. The server authorizes every request, sends TDClaim-owned data in bounded batches, and revokes the client snapshot when the display is disabled, operator access is lost, or the session or dimension changes.
• Refresh the operator claim-map snapshot after /tdclaim reload, invalidate stale World Map highlight hashes when map data changes, and cap expanded client-side chunk work at 262,144 chunks.
• Replace whole-claim force loading with multiple operator-defined rectangular areas inside each claim. Overlapping areas count shared chunks once, and their union is limited by the reloadable maxForceLoadedChunksPerClaim server setting, which defaults to 256 and supports up to 4,096.
• Add a scrollable force-loading editor that uses the existing two-corner selection, reports current chunk usage, and removes individual areas.
• Store force-loaded areas in data schema 10 and restore their tickets after restarts, claim changes, deletion, and history operations. Legacy whole-claim force loading migrates without discarding its area; claims above the active server limit keep their configuration but receive no TDClaim tickets until they fit the limit again.

3.3.0

• Add a per-claim force-loading switch in the claim overview. Enabled claims keep all intersecting chunks fully ticking without nearby or online players while the server is running.

• Restore force-loading from saved claims after server restarts and update tickets when claims are resized, deleted, or restored through history. Existing claims default to force-loading off.

• Keep spawn-rule help outside the scrolling rules list.

• Show pending requests before previous status messages, report unconfirmed timeouts, and offer a refresh action.

• Distinguish unloaded, loading, failed, and empty reports, and explain block searches without matches.

• Keep claim titles readable with a separate color swatch and remove decorative background dot grids.

• Keep one Tools entry and visibly mark the selected tool tab.

3.2.3

• Allow friendly mobs such as sheep and pigs to spawn inside mob-free radii while continuing to block hostile mobs.
• Check hostile entities when they join the world as well as during spawn finalization, closing bypasses such as slime and magma cube splitting. Existing entities loaded from disk and operator /summon commands, including NBT and passengers, remain exempt.

3.2.2

• Preserve unsaved claim names, search filters, and dimension spawn radii across refreshes and navigation. Keep edits scoped to their claim or dimension, and accept updated server values once local edits are saved.
• Preserve text focus, cursor position, and selection when rebuilding the UI. Include block search and template names when pausing automatic refresh during typing; background refresh no longer applies unfinished search filters.
• Keep the selected report entry and its scroll position when reloading history or templates, and remember recent scroll positions when returning from another view.
• Deliver administration responses to the underlying screen while a confirmation is open. Cancel a confirmation if its target changes, and close both administration and confirmation screens when operator authorization is lost.

3.2.1

• Preserve administration UI scroll positions when data refreshes or permission edits rebuild the current view, instead of jumping back to the top. Clamp positions when refreshed content becomes shorter.

3.2.0

• Add /tdclaim reload for operators and the server console to read and apply the server configuration while the server is running. NeoForge config reload events also refresh TDClaim's runtime settings.
• Update spawn protection, mob-free radii, the current world-spawn center, selection and visualization settings without restarting or replacing claim data, dimension spawns, block permissions or player sessions. Invalid manual reloads leave the previous runtime configuration active.

3.1.0

• Recognize TDEconemy Account Terminals with the dedicated account_terminal_use interaction permission. It inherits block interaction rights in claims and is allowed by default at protected spawns, with explicit rules taking precedence.
• Add persistent position-and-block-type rules for the default spawn and dimension spawns, editable through the existing block permissions dialog for public, player and group access. The target-block command also finds protected spawns automatically; ordinary claims retain priority.
• Store spawn block rules in data schema 8 and update network protocol to 7. Update TDClaim on the server and every client together.

3.0.3

• Fix administration controls disappearing or overlapping at larger GUI scales and in small windows. Fit the complete panel to the available viewport while preserving control positions and matching mouse input.
• Apply the same automatic fitting to confirmation dialogs and recalculate it when the window is resized, without changing Minecraft's GUI-scale setting.

3.0.2

• Fix travel through existing Nether, End, and custom-dimension portals being blocked by the departure area's block_use permission. Dimension changes no longer require block interaction rights; portal construction, ignition, and right-click interactions retain their normal protection checks.

3.0.1

• Fix Blaze Burner crashes with Create Liquid Fuel 3.0.0 and Create 6.0.10 caused by casting TDClaim's guarded fluid handler to SmartFluidTank. Adapt both internal ticking and container-refill tank lookups while retaining external sided transfer protection and cached permission checks.

3.0.0

• Keep admin mode available in the administration UI and through /tdclaim adminmode <on|off|toggle|status>.
• Remove redundant claim, selection, permission, player, group and dimension-spawn commands. Manage these functions in the UI opened with /tdclaim. Existing scripts using the removed commands must be updated.
• Add /tdclaim blockpermission [claim] to register the block under the operator's crosshair for block permissions. Without a name, it selects the claim at the target block, independently of the player's position. An optional name restricts the target to that claim. It shares the UI's six-block reach and claim/dimension checks, inherits existing claim permissions, and preserves an existing entry when repeated.
• Existing claim data and permissions remain compatible; the major version marks the changed command interface.

2.10.0

• Block natural fluid and dispenser entry from wilderness, including sources beyond the building border. Prevent cross-boundary piston movement.
• Add exact-position/type automation ports for technical connections to wilderness. Trusted builders establish ports when installing edge block entities; admins can revoke individual ports without reopening them on replacement.
• Guard standard sided NeoForge item, fluid and energy capabilities and recheck cached handlers after permission changes. Different claims remain isolated.
• Add a server-side permission inspector for selected players and actual blocks, including inherited rules and neighboring claim border denials.
• Store the last 256 claim changes with before/after snapshots, admin identity and conflict-checked undo across restarts.
• Add up to 32 named permission templates, block-rule search and permission copying between individual block entries.
• Separate configured SecurityCraft keycard-reader/lock use from configuration access. Add an optional boundary check for Create moving block breakers and document remaining modpack integration limits.
• Migrate existing data to schema 7 without changing existing player permissions. Existing external machinery needs explicit endpoint ports. Update the network protocol to 6; server and clients must update together.

2.9.0

Added

• Added an operator-only Block X-ray toggle to the claim overview and block-permissions dialog. Recorded block positions are visible through walls with distinct colors for explicit allows, other rules, and mismatched block types.
• The display remains active after closing the UI, refreshes authorized block rules, respects the configured visualization range and loaded chunks, and clears on claim/dimension changes, logout or authorization loss.

2.8.0

Added

• Added detailed action permissions, simple and expert editors, and persistent block rules for public, player, and group access at an exact position and block type.
• Added a block-permissions dialog with server-validated targeting, status, removal, and individual rule editing. Replacing a block with the same type restores its rules.
• Added a boundary-building permission protecting the one-block exterior border, including corners, from unauthorized placement and modification.

Changed

• Shops, Waystones, and recognized seats have separate usable defaults in claims. Block rules override claim rules for their matching position and type.
• Claim-to-wilderness vanilla transport is allowed; transport between different claims stays blocked. Spawn protection retains its existing boundary restrictions. Modded pipes and external networks require separate compatibility validation.
• Claim storage uses schema 6 and the network uses protocol 5. Older claim permissions migrate to the detailed actions; server and clients must update together.

2.7.0

Added

• Every dimension spawn now stores independent overrides for all ten protection permissions. Operators can cycle each rule between the built-in default, explicit allow, and explicit deny in the administration UI.
• Added /tdclaim dimspawn permission <permission> <allow|deny|default> as a command equivalent to the UI controls. Dimension-spawn info and list output includes active overrides.

Changed

• Explicit dimension-spawn denies now override the built-in item-drop, shop, door, Waystone, seating, and rideable-entity exceptions, while explicit allows open the selected action. TDClaims covering the same position still take precedence.
• Increased the client/server network protocol to 4 for synchronized dimension-spawn permission states.
• The claim data file moved to schema 5 to store dimension-spawn permission overrides. Schema 4 dimension spawns migrate with the unchanged built-in policy.

Fixed

• Long administration labels and help text now wrap or truncate within their assigned panel bounds instead of drawing across the screen.

2.6.1

Fixed

• Replaced the oversized administration layout with the same compact 520-by-340 panel proportions and actual LDLib stylesheet behavior used by TDEconemy.
• Removed the duplicate claim navigation bar. Claims, spawn rules, and dimension spawns are now the only persistent tabs; public, player, and group permissions use clear contextual editors with a single Back action.
• The Claims tab now shows concrete player and group access entries directly beside the selected claim and keeps claim search, filtering, management, and access editing inside one readable dashboard.
• Removed the full-page scrolling workspaces from spawn administration. Spawn rules now fit into two columns, while dimension spawn points use a focused previous/next selector with radii and rules visible together.
• Aligned confirmation-screen size, colors, and button spacing with TDEconemy's confirmation dialogs.
• Waystones blocks are now always usable inside claims, Overworld spawn protection, and dimension-spawn protection even when their menu capability classifies the interaction as container_use. This exception does not allow breaking, replacing, or placing blocks.

2.6.0

Added

• Added dedicated top-level administration tabs for claims, the fixed Overworld spawn policy, and per-dimension spawn protection.
• The claim overview now names concrete player and group overrides with their access states instead of reporting only counts.
• The spawn-policy tab shows the active center, both configured radii, and every allowed, conditional, or blocked permission in one readable overview.
• Dimension spawn points can now be set or moved to the operator's current position, selected across dimensions, resized, and removed directly in the server-authoritative UI.

Changed

• Restyled the administration and confirmation screens with the shared dark petrol gradient, subtle texture, panel depth, and gold accent used by TDEconemy.
• Increased the client/server network protocol to 3 for the new spawn-area snapshots and dimension-management actions.

2.5.2

Fixed

• Recognized modded chairs, seats, stools, benches, sofas, couches, loveseats, and ottomans can now be used inside the fixed Overworld and dimension-spawn protection areas. Explicit TDClaims continue to control the same blocks through block_use.

2.5.1

Fixed

• Fixed the spawn entity-use exception checking nearby entities instead of the entity actually used. Villagers and other protected entities can no longer become interactable merely because a boat, minecart, horse, or other rideable is nearby.
• Kept a pure mobFreeRadius limited to mob spawning, mob-driven explosions, and mob griefing. It no longer acts as general fire, fluid, dispenser, hopper, item-transfer, or piston protection outside a TDClaim or spawn protection radius.
• Permission and rename updates no longer revalidate every claim overlap or rebuild the complete spatial chunk index, avoiding avoidable server-tick work as claim counts grow.
• Admin mode is now cleared while a de-opped player is online, preventing an old enabled state from returning after that player is re-opped.
• Xaero spawn-waypoint delivery now waits indefinitely for the Overworld waypoint world and retries temporary save failures at a bounded rate instead of silently giving up or accepting an unsaved marker.

Documentation

• Updated the manual acceptance checklist for schema 4 migration and complete Xaero waypoint coverage.

2.5.0

Added

• New server option spawnWaypointEnabled (default on). When enabled, every joining player receives a Xaero's Minimap waypoint named "Spawn" at the overworld world spawn. The client needs Xaero's Minimap 26.4.2 or newer; the feature is silently skipped otherwise. The waypoint is repositioned if the world spawn moves and an existing waypoint of the same name is reused.

2.4.0

Changed

• The fixed spawn protection policy now allows shop_use. Active TDEconemy shop boards, their shift-use editor, and their directly attached storage stay usable inside spawnProtectionRadius and a dimension spawn without an explicit TDClaim. Every other interaction inside the protected area stays denied.

2.3.0

Added

• The player workspace now lists the recorded claim creator, every player with a personal override, every online player, and every player with stored world data instead of showing only existing overrides.
• Every player entry is marked online or offline and shows its access state as full, blocked, custom, or public default. Its tooltip repeats both, marks the recorded creator, and shows the player UUID.
• The overview now names the recorded creator and summarizes how many player and group overrides exist and how many public permissions are allowed.
• The player workspace explains the evaluation order of personal override, group override, and public default.
• New server option mobFreeRadius defines a square block radius around the overworld spawn. Inside it, rule-based mob spawns are vetoed and mob-driven explosions, mob griefing, and Enderman block theft are suppressed. It does not restrict player actions or chunk claims, /summon stays exempt, and 0 disables it. Set spawnProtectionRadius to at least the same value so player-driven mob creation such as spawn eggs, golems, the wither, and breeding is also stopped.
• New /tdclaim dimspawn command manages one protected spawn point per dimension: set at the operator's position, radius and mobradius to size the independent protection and mob-free zones, remove, list, info. Inside the protection radius the fixed deny-all spawn policy and OpenPAC chunk block apply as at the overworld spawn; inside the mob-free radius rule-based mob spawns are vetoed and mob-driven damage is suppressed. /summon is exempt. A dimension spawn overrides spawnProtectionRadius and mobFreeRadius for its dimension.

Changed

• Player targets in the administration UI are chosen exclusively from that list. The free-text player name field was removed, so a typo can no longer address a wrong or non-existent player.
• The administration state snapshot transports up to 1,024 selectable players, refreshing the offline part every 30 seconds, so server and clients must run matching 2.3.0 builds.
• Personal overrides may now also target a player who has world data but is no longer present in the server profile cache.
• Inside the fixed spawn protection policy, players may now still open doors and waystones and mount horses, pigs, striders, camels, boats, and minecarts, so the protected spawn area stays passable.
• The claim data file moved to schema 4 to store per-dimension spawn points. Schema 1, 2, and 3 files migrate on load with no dimension spawns.

2.2.3

Fixed

• Ground boundary lines now enforce readable minimum width and opacity and are tall enough to remain recognizable against varied terrain; older lower client-config values are corrected on load.
• Adjacent ground segments now bridge terrain-height changes instead of leaving disconnected horizontal pieces at slopes and ledges.

2.2.2

Fixed

• Ground boundary lines now use the highest loaded terrain surface on both sides of each edge and render slightly above the block surface, preventing them from disappearing below slopes, ledges, and ravines.

2.2.1

Added

• Added Shift-right-click with the Surveyor's Staff to open the administration UI without changing claim corners.

Fixed

• Corner beams now extend from the terrain past the current camera height and refresh as the viewer changes elevation.

2.2.0

Added

• Added the modpack's LDLib2 2.2.37 as the required client UI library.

Changed

• Rebuilt the complete administration and confirmation interface exclusively with LDLib2 controls.
• Reorganized claim management into a focused claim browser and clearly separated overview, public, player, and group workspaces.
• Simplified compact-screen navigation while preserving every server-authoritative management action and automatic refresh behavior.

2.1.1

Fixed

• Selected claims, tabs, players, and groups now use an explicit marker instead of the disabled button style that made other entries appear selected.
• Administration and confirmation screen foreground text now renders sharply above the widget layer with a readable shadow.

2.1.0

Added

• Added optional read-only TDEconemy groups as UUID-based permission subjects without claim ownership, purchase, sale, balance, or shop logic.
• Added group permission commands and UI actions for individual overrides, allow-all, deny-all, and reset.
• Added direct claim-tool delivery and selection-corner feedback.

Changed

• Claim data schema 3 stores group overrides and migrates schemas 1 and 2 without granting new implicit access.
• The administration interface now preserves form input, pauses background refresh while text is edited, supports keyboard search, and scrolls on compact layouts.
• Bulk confirmations identify the affected claim and player or group. Enabling admin mode requires explicit confirmation.
• Nearby visualization snapshots prioritize the closest claims before applying the configured synchronization limit.
• Denial and selection feedback now uses localized components.

Fixed

• Fixed periodic UI refreshes discarding an in-progress claim name and keyboard focus.
• Fixed compact or highly scaled screens placing permission controls outside the reachable area.
• Fixed rate-limit responses leaving the administration interface permanently disabled or replacing it with an empty snapshot.
• Fixed arbitrary forged player UUIDs creating unknown player override records.
• Removed the silent 256-player truncation from claim detail snapshots while keeping a bounded network contract.

2.0.0

Added

• Added the /tdclaim client administration interface with claim search, dimension filtering, paging, complete claim management, public permissions, player overrides, and session admin mode.
• Added the non-craftable Surveyor's Staff and server-authoritative terrain-following claim and selection visualization.

Changed

• TDClaim now requires a compatible installation on the server and every client. The network protocol is version 2.

1.1.5

Fixed

• Prevented server-side player tools that directly mutate blocks through Level.setBlock() from bypassing block_place protection.
• Applied the same target-level protection to tools that rely on Level.mayInteract() instead of a normal NeoForge placement event.

1.1.4

Added

• Added configurable square spawn protection around the Overworld spawn, with explicit TDClaims taking precedence.
• Added optional Open Parties and Claims 0.30.3+ integration that prevents overlapping OpenPAC chunk claims and delegates access decisions to TDClaim in intersecting chunks.
• Extended environmental protection to unclaimed parts of the configured spawn zone.

Changed

• Improved denial messages for actions blocked by spawn protection.

1.1.2

Changed

• Increased default claim-outline particle density by reducing particle spacing from 2.0 to 1.0 blocks.

1.1.1

Fixed

• Restricted the TDEconemy shop-management exception to genuine active shop boards and their directly attached storage.
• Validated the shop block ID, persistent schema marker, and loaded TDEconemy mod before granting the exception.
• Kept offhand interactions, canceled events, inactive shops, and unrelated block entities under normal claim protection.

1.1.0

Added

• Added the item_drop permission for manual item drops inside claims.
• Added protection against hoppers moving items across claim boundaries.
• Added protection against item entities crossing claim boundaries in either direction.
• Added protection against droppers inserting items across claim boundaries.
• Added a narrowly scoped TDEconemy exception for members managing group-owned shops and their attached storage.
• Added schema-version-2 persistence and safe migration defaults for the new permission.

1.0.1

Fixed

• Improved claim visualization so outlines follow terrain and remain useful for large claims without sending distant particle sections.
• Improved command feedback and validation for claim creation, deletion, renaming, redefinition, selection, and permission management.

1.0.0

Added

• Added rectangular, full-height claims with operator-managed selections and administration commands.
• Added public permissions, UUID-based personal overrides, and session-bound operator admin mode.
• Added block, container, shop, entity, combat, explosion, fire, fluid, piston, dispenser, and other environmental protections.
• Added server-side Vanilla-particle claim visualization without requiring clients to install TDClaim.
• Added strict persistent claim storage, validation, transactional updates, and fail-closed recovery behavior.
• Added configurable selection tools, visualization settings, denial cooldowns, and TDEconemy shop-marker compatibility.

Alle TD-Mods