Reading and accepting TDRules
Mod version shipped with FlammiCraft: 1.24.0
TDRules connects the Patchouli rules book to server-owned acceptance records. The same TDRules version and Patchouli are required on the server and clients. Network negotiation rejects different mod versions. Operator status alone does not bypass rules.
Join as a player
- Use the Patchouli rules book opened directly after login. While acceptance is required,
/tdrules openreopens it. - Use
/tdrules showto open the book independently or browse it later. There is no additional Show button to press. - Read all five numbered mandatory pages and check the progress indicator. Each summary links to the full rules.
- Accept only after completing required reading, entering the password supplied by the server team when configured.
- Wait for success before expecting restrictions to end and safe return to complete.
/tdrules accept and /tdrules accept <password> use the same checked acceptance path. Respect password error feedback and any lockout rather than repeatedly retrying. Declining uses /tdrules decline and its requested confirmation; confirmed decline persists the decision and disconnects you.
Required acceptance restricts movement, inventory, interaction and non-allowed command roots. Chat and rule controls remain available. Closing the screen, reconnecting or restarting does not replace acceptance.
The required-page counter and progress bar appear only while acceptance is required, including first login and rule updates. They stay hidden when browsing after acceptance.
Choose Read aloud below the book to hear the open pages during required reading or while browsing later. In Minecraft's Accessibility Settings, enable the narrator for system messages or all messages. Your device must support text-to-speech.
If reading progress cannot be saved, the book displays an error. Ask the server team to check storage permissions and free space, then choose Continue reading to report completion again. Pages already displayed remain recorded for this client session. Repeated reports acknowledge saved progress without another write.
Starter kit and renewed acceptance
In TDRules 1.18.0, the Neu in Regelversion 2 chapter summarizes the rule changes. Players who already accepted rule version 2 can read the updates with /tdrules show. Their acceptance remains valid.
In TDRules 1.24.0, the bundled rules limit Create trains to 64 blocks total, including the locomotive and all carriages. The limit is described in the Create chapter and on the fifth required page. Existing acceptances of rule version 2 remain valid.
A starter kit is planned only after the first successful acceptance in a player record's lifetime. New rule versions, resets and reconnects do not create another kit. Overflow kit items may be dropped at the player, so inspect the actual delivery.
Ambiguous interruption can mark a kit NEEDS_REVIEW. Operators must inspect the persisted plan and existing items before confirming a retry, which can otherwise duplicate them. A failed loot-table call does not invalidate rule acceptance.
Operator workflow
/tdrules admin opens administration. Level 2 reads status and enables personal session admin mode; level 3 handles reset, reload and kit recovery; level 4 changes configuration. Personal admin mode ends on logout/server shutdown without changing saved acceptance.
On standalone servers, serverconfig/tdrules-server.toml defines additional allowed command roots and the starter-kit loot table. Use lowercase roots without slashes and list aliases separately. In a cluster, change settings from the TDRules administration screen. /tdrules reload validates the shared database settings against the embedded rule version. New logins require the current database state. An origin saved on another backend is used when the player enters that world again.
Back up the database and world files and upgrade all TDRules backends from 1.20.0 together. An empty database takes its initial settings from the first backend, so start the backend with the intended settings first. See cluster storage for the upgrade and recovery details.
Administration saves settings, radius, enforcement and return locks through one checkpoint. A failed checkpoint retains the previous active values. On standalone servers it also restores the previous TOML contents. A failed reset preserves the previous player record; online resets save the new status and origin together. If administration explicitly reports failed file recovery, repair the TOML using the error and server log before reloading or restarting, because the file may contain rejected values.
These failure paths and version negotiation have automated checks. Rendering and multiplayer behavior with the new JAR still require full client and server restarts and in-game acceptance.
Mod version, acceptance version and Patchouli book version are separate. Acceptance version zero disables enforcement; once activated it cannot be reduced. Pause with /tdrules config enforcement off instead of resetting versions or data.
For unavailable acceptance check required pages, active version and server feedback. Preserve invalid persisted records rather than replacing them with empty files. The reference lists commands, password handling and kit recovery.