Changelog

1.0.0

• First public TeamVibes release.
• Linked physical chest storage with search, categories, favorites and quick transfers.
• Standalone multiplayer owner requests and optional MultiUserChest integration.
• Batched storage actions and physical sorting.
• Corrected stale chest state during ownership changes.
• Simplified action messages; sorting is the only routine success popup.
• Added release icon and Thunderstore, Hexium and Nexus packaging.
• Detailed debug logging defaults to off for new configurations.

Changelog

Unreleased fix — owner-state-fix2 (0.11.0 test build)

• Address the stale local in-use flag after ownership loss: observers resume loading current ZDO data, and a newly opened owner refreshes before accepting item operations.
• Reject a clicked source reference replaced by a refresh; do not operate on its replacement item accidentally.
• Verify standalone owner inventory bytes against persistent ZDO bytes before success replies; retain evidence and fence mismatches instead of acknowledging memory-only changes.
• Log state-refresh/persistence counts, owner, loading/in-use flags, revisions and hashes.
• 70 managed checks and clean compilation; five new checks cover the ten-stack handoff, stale clicked item, missing save callback and bulk-lock isolation.
• Live retest required. Does not restore already missing items or discard old journals. Apply to owner-startup-fix1 source.

Unreleased fix — owner-startup-fix1 (0.11.0 test build)

• Fix client initialization before peer handshake supplies the world; retry on the same session and keep the periodic transaction loop alive after errors.
• Register durable request evidence before blocking slots, blocking consumption, or removing offered swap items.
• Return a negative owner reply with the offered parcel when preflight fails before chest mutation; cache that decision against duplicate requests.
• Remove duplicate registration in the ordinary same-chest move helper.
• Add correlated request/response diagnostics, rate-limited pending and blocking reports, and detailed chestlink_tx_status.
• Clean Debug compilation and 65 managed checks, including seven regressions for this failure. Live two-player verification remains required.
• Apply this single patch to the tested 0.11.0 owner-request source. Preserve existing journals; uncertain past transfers are not automatically refunded.

0.11.0 — owner-request multiplayer test candidate

• Standalone owner-request transfers adapted from the MIT-licensed MUC core; optional installed MUC handles ordinary transfers instead.
• Direct food/potion consumption without requiring an empty player slot; return items when late consumption is invalid.
• Standalone request correlation, duplicate request/reply protection, exact item metadata and chest/transit conservation checks.
• Retain batched STORE/RESTOCK/TAKE ALL/PLACE STACKS, cross-chest moves and SORT with player/chest rollback and coordination.
• Isolate both ordinary backends from bulk commits; refresh all linked physical chests and resolve the correct source for outside drops.
• Record standalone pending/owner-reply evidence and retain uncertain transactions for investigation.
• Preserve the existing single-player transfer path, UI, filters, favorites and placement policy.
• Remove the obsolete ownership-probe implementation.
• One apply.sh directly updates the supplied 0.10.6 source; no intermediate 0.11.0 patch is needed.
• 58 managed checks and a clean Debug compilation. Real multiplayer validation and performance measurements remain required.

Known limit: automatic recovery across independently saved character/world data is not implemented. MUC-backed ordinary transfers inherit MUC's guarantees/limitations.

0.10.6 — supplied baseline

Existing UI/classification/placement and physical borders retained. The supplied TransactionsV7-fast baseline had reported player/chest duplication; it is superseded by this test candidate.