BuildUp

TDRules Changelog

Alle TD-Mods

Aktuell veroeffentlicht: 1.6.2

1.6.2

Fixed

  • Preserve unsaved administration settings across tab changes, resizing, cancelled confirmations, and unrelated server responses.
  • Bound administration status messages in a selectable, horizontally navigable field with the full message available as a tooltip.
  • Name administration input fields for narration and add a visible search hint.
  • Explain empty player and starter-kit lists and provide a clear-filter action for searches without matches.
  • Keep button text at its normal font size, abbreviate overflowing labels with full-text tooltips, and widen the rule acceptance actions.
  • Translate player and starter-kit status values in the administration interface.

1.6.1

Fixed

  • Keep button labels centred and fit their full text inside the button at small GUI sizes, avoiding scrolling-text clipping under the dialog's additional scaling.

  • Removed duplicate pages about support, abandoned properties, safe zones, Create Mechanical Spawner, and dimension resets from the bundled rule book. Rule acceptance version 2 remains unchanged because the rule content is equivalent.

1.6.0

Added

  • Added five clearly numbered required-reading pages with links to the detailed rules, a quick reference, and a rule-version-2 change summary.
  • Added direct change-summary, quick-reference, and Discord invite buttons to the acceptance screen, with room for password entry at small GUI sizes.
  • Added a content-review manifest and build tests that require an explicit acceptance-version decision whenever bundled rule-book content changes.

Changed

  • Required reading now counts the five designated pages instead of any five book pages. Completed pages can still be reopened.
  • Restricted machine-based natural-resource farming to the mining dimension, while explicitly allowing Create excavation for concrete building projects and normal factories and production.
  • Clarified admin-only claims and permissions, Discord tickets, the twelve-chunk limit in each horizontal direction, and the distinction between unprotected storage theft and prohibited griefing or protection bypasses.
  • Documented world-spawn protection radii of 250 blocks for PvP and 260 blocks for mob spawning, portal safe-zone boundaries, and continued consent requirements outside safe zones.
  • Explained farming-world boss restrictions and the secured-room exception for Create Mechanical Spawner resource production.
  • Clarified AFK and offline factories, individual performance interventions, dimension resets, abandoned properties, neutral complaint discussions, and case-by-case reimbursements.
  • Increased the rule acceptance version from 1 to 2 so players must accept the updated rules again.

1.5.2

Fixed

  • Fit the rule acceptance, decline, confirmation, and administration screens into small GUI dimensions without clipping controls or overlapping fixed layout rows.
  • Apply the same local scaling to rendering and mouse input, including dragging and scrolling, without changing the player GUI scale setting.

1.5.1

Changed

  • Removed the hard-coded BuildUpExp promotion from the successful rule-acceptance message and kept the German and English text server-neutral.

1.5.0

Added

  • Added the personal, session-only /tdrules adminmode on|off|status commands for operators.

Changed

  • Operator permission alone no longer bypasses rule acceptance or any gameplay restriction.
  • The legacy debug setting is now ignored, remains readable for compatibility, and is removed the next time administration settings are saved.
  • Personal admin mode is cleared on logout and server shutdown without changing the operator's saved rule decision or return lock.

Fixed

  • Applied one consistent acceptance decision to the forced screen, rules-book issuance, movement, interactions, inventory, combat, food, and command restrictions.

1.4.2

Changed

  • Restyled all TDRules buttons with the same dark, rounded GDP appearance used by TDEconemy while retaining native Minecraft widgets.

Fixed

  • Prevented administration-setting labels, fields, action buttons, and the read-only rules-version note from overlapping.
  • Stacked labels above their fields on narrow administration screens so translated text remains readable.

1.4.1

Added

  • Added /tdrules config debug on|off and included the active debug value in /tdrules config show.
  • Added an automatic, settings-preserving migration that writes debug: false into existing world settings files that predate the toggle.

Changed

  • New, reset, declined, and outdated players are now locked to their exact current dimension, position, yaw, and pitch until they accept.
  • Exact acceptance locks now survive logout and restart instead of being converted into spawn locks.
  • The reading gate now requires five distinct displayed rule-book pages for each rule acceptance version.

Fixed

  • Enabling debug now captures the single-player operator's current position, immediately enforces restrictions, and opens the acceptance screen; disabling it removes pending operator locks.
  • Online resets from both the command and administration screen now create the same exact-position lock without resetting one-time starter-kit state.
  • Prevented Escape from closing any Patchouli screen belonging to the forced rules book.
  • Applied debug mode consistently to command restrictions, so integrated-server operators cannot bypass non-TDRules commands while testing enforcement.
  • Kept all commands exclusively under /tdrules and retained player-name tab completion for reset and other target commands.

1.4.0

Changed

  • Replaced the LDLib2 screen layer with native Minecraft widgets and made the administration screen adapt to smaller GUI dimensions.
  • Restored the documented movement policy: new, reset, and declined players use the spawn sphere, while only outdated accepted players receive an origin lock.
  • Made the default build and unit-test suite independent of a personal Minecraft instance and exact installed mod JAR filenames.
  • Clarified that page display and acknowledgement are official-client safeguards, while acceptance authorization, password checks, and persistence remain server-authoritative.

Fixed

  • Synchronized online clients when a reload changes operator debug bypass without changing the rule version.
  • Made command and administration-screen player resets follow the same movement and screen-opening path.
  • Masked password entry in the player and administration screens.
  • Preserved the actual target player identity in command audit events.
  • Prevented the administration dashboard from failing when saved player records exceed its network limit.
  • Updated release artifacts, requirements, validation documentation, and the manual runtime checklist for the current version.

Removed

  • Removed the LDLib2 dependency from source code, Gradle, and NeoForge metadata.

1.3.0

Changed

  • Rebuilt the rule acceptance and decline screens on the LDLib2 UI framework: a laid-out panel with a real read-progress button, an acknowledgement switch, and styled accept/decline actions instead of the hand-positioned vanilla widgets.

Added

  • LDLib2 (ldlib2, 2.2.37 or newer) is now a required dependency on both sides.

Note

  • The server password field no longer masks input, as LDLib2's text field has no masked mode.

1.2.1

Fixed

  • The player acceptance screen can no longer be dismissed while acceptance is required. Esc is ignored, and if the screen is closed by any other action it reopens on the next client tick, so players no longer end up restricted at spawn with no screen and have to reconnect.

Changed

  • Closing the Patchouli rules book now always returns to the acceptance screen regardless of how the book was opened.
  • Operators (permission level 2 or higher) are no longer shown the acceptance screen on login and may dismiss it if they open it manually, consistent with their bypass of every other restriction.
  • Removed the now-unused reopen chat action that the acceptance screen posted on close.

1.2.0

Added

  • Added persistent, version-bound reading progress for the bundled Patchouli rules book.
  • Added a dedicated close button that returns players from the rules book to the acceptance screen.

Changed

  • Players must display every page of the current rules book before reading confirmation and acceptance are enabled.
  • A reset or newer rule acceptance version requires the book to be read again.
  • Updated the client-server network contract for the reading-progress state.

1.1.2

Changed

  • Updated the bundled German rules for Nether trains, mob and event behavior, the resource world, and Create infrastructure.
  • Simplified internal command, message, configuration, inventory, kit, network, and audit implementations without changing the rule acceptance version.

1.1.1

Changed

  • Changed NeoForge compatibility metadata from an exact version to an open-ended minimum of the configured build version.

1.1.0

Added

  • Added a guided player acceptance screen with direct book access, reading confirmation, password input, and decline confirmation.
  • Added a server-fed administration screen for overview, settings, player management, and starter-kit recovery.
  • Added server-authoritative network actions and validation for player and administration workflows.
  • Added confirmed manual starter-kit reissue for online players at permission level 3 or higher.
  • Added German interface text and English fallback text.

Changed

  • Moved routine player and administrator workflows from chat-only interaction to dedicated screens while retaining the existing commands.

1.0.1

Fixed

  • Made the audit writer stop accepting events after an I/O or runtime failure instead of continuing with an invalid writer.
  • Limited each player's SavedData decision history to the newest 100 entries.
  • Updated movement checks to use the supported loaded-chunk API.

1.0.0

Added

  • Released the server-authoritative rules acceptance system for Minecraft 1.21.1 and NeoForge.
  • Bundled the German Patchouli rules book under tdrules:rules.
  • Added world-bound player decisions, renewed acceptance, movement and interaction restrictions, password protection, starter-kit delivery, optional inventory adapters, and JSONL audit logging.
  • Required matching TDRules versions on the server and all clients.