TDClaims

All notable user-visible changes to TDClaim are documented in this file. The format follows Keep a Changelog, and TDClaim uses Semantic Versioning.

This changelog was introduced with version 1.1.5. Entries for earlier versions were reconstructed from the repository's version-bump history.

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