ChestSort Changelog

v1.1.0 to v1.1.1

• ATTN: This version is combined with v2.
  

• Added /cs blacklist mode <preventSort|strictPreventSort|preventEntry|strictPreventEntry> to configure how the global blacklist interacts with sorting and container entry.
  • preventSort: prevents blacklisted items from being moved by Sort/Autosort unless the item is whitelisted and whitelist wins priority
  • strictPreventSort: like preventSort, but blacklist always wins (ignores whitelist priority)
  • preventEntry: prevents blacklisted items from being put into the container unless the item is whitelisted and whitelist wins priority
  • strictPreventEntry: like preventEntry, but blacklist always wins (ignores whitelist priority)

ChestSort Changelog

v1.1.1 to v2-alpha

• Added client-only sorting fallback for servers without ChestSort installed.

  • Uses vanilla inventory click packets (shift-click / QUICK_MOVE) instead of custom payloads.
  • Sorting actions run over time (queued per tick) to reduce desync and packet spam.

• Added client-only Organize fallback for servers without ChestSort installed.

  • Uses vanilla clickSlot packets (PICKUP) to merge stacks and compact the open container.
  • Also runs as a paced per-tick action queue.

• Added per-container filter persistence on unmodded servers.

  • Container filters are saved client-side keyed by dimension + chest coordinates.
  • Filters now load automatically when you reopen the same chest/barrel.

• Added client-local preset persistence for servers without ChestSort installed.

  • Importing a preset (or presetList) stores it locally even if the server cannot accept preset payloads.
  • Preset edits are saved locally as well.

• Added safe networking: ChestSort custom payloads are only sent when the server advertises support.

  • Prevents disconnects/kicks caused by sending unknown custom payloads to unmodded servers.

• Improved multiplayer usability: the ChestSort GUI now shows reliably for vanilla containers.

  • The UI no longer depends on receiving a server context packet to appear.

• Client-side filtering now supports tag search suggestions again (tag autocomplete uses the proper registry tag stream).
• Client-only mode uses separate action queues to prevent conflicting automation (e.g., Sort and Organize running at the same time).

• Autosort still requires server support (it needs the server to enforce and apply the rule while items are inserted).
• Client-only Organize/Sort are best-effort on laggy servers and can be slower on large containers because actions are paced per tick.