v3.4.0

3.4.0 - Persistence Diagnostics and Schema Compatibility - 2026-08-31

Added

• When Tamework telemetry and Diag consent are enabled, terminal persistence failures now send a bounded, redacted debug database package with the error classification. This includes generic and bonded persistence startup, read, write, checkpoint, runtime, and shutdown failures.
• Added /tw debug persistence simulateerror for a harmless, console-safe end-to-end diagnostic test. It does not change persistence data.

Changed

• Updated the embedded Patchwork runtime to 1.4.0. Asset patches can now use an empty path with safe object-merge operations to merge the document root.
• Persistence diagnostics now use the direct /tw debug persistence status|health|detail|export commands.
• Automatic persistence reports run outside the storage path and use a bounded queue. They never block or change the result of a persistence operation.
• Disabling Tamework telemetry remains the opt-out for all automatic Tamework persistence diagnostics.
• Automatic persistence diagnostics now use the independent Diag consent category. Error consent does not enable or disable these reports. Existing projects that already reviewed consent must select Save and Close in /telemetry consent before Diagnostics can run. A report that cannot enter the telemetry queue remains eligible on the next matching failure.

Fixed

• A failed persistence request no longer disables unrelated companion actions unless Tamework detects database corruption, an incompatible schema, or an unresolved commit outcome.
• Existing replacement databases from Tamework 3.2.x now upgrade to the expanded persistence schema without deleting profiles or resetting player data. The upgrade creates a verified sibling backup before it changes the database.