Skip to content

Create: Distant Stock v0.3.62 · Network Join & Bounded Stock Paging

Choose a tag to compare

@EVGA2048 EVGA2048 released this 28 Oct 12:37
· 2 commits to main since this release

v0.3.62 — End-to-End Join, Warehouse Membership, Delivery Addresses & Bounded Stock Paging

This update fixes the gaps left after v0.3.61 catalog discovery. Seeing a remote network name no longer implies a usable warehouse: joins, local warehouse enrollment, announcements, stock queries, order destinations and UI updates now share the same formal Distant Stock network scope.

Joining and warehouse membership

  • A portable terminal with no local Create frequency can join a VL4 network using the join code from ES2, in-game or with /distantstock network join-terminal <code> or /distantstock network join <code>.
  • Join responses can survive queue congestion (5-minute acceptance window; 6-minute durable message lifetime), and the terminal's accepted network ID is persisted after chat-command joins too.
  • New networks enroll the selected local Create warehouse when the player has Create administrator permission. Existing empty networks can be repaired without deletion: open the network's warehouse picker and select a local 未加入 · 点击纳入本网络 warehouse, or use /distantstock network enroll with the appropriate terminal.
  • /distantstock doctor / network now show local and remote warehouse counts and outstanding joins.
  • Receiving addresses matter for actual orders: the group create command now creates a group in the player's selected formal Distant Stock network instead of silently placing it in Legacy. dock send-to uses the same scope when resolving a target.

Large inventories: bounded, shared and paged

  • Stock wire v2: max 128 item rows/page, max 48 KiB per result, max four new remote queries per two-second beat.
  • Shared server-side cache of Create inventories; only watched warehouses are scanned, at most two large scans/beat, not on the UI open event.
  • Client screen receives at most 128 rows per packet; global UI page budget eight packets per two seconds with round-robin fairness and incremental progress.
  • A single network snapshot may contain up to 32,768 item types; the safety cap is reported in diagnostic logs if exceeded rather than creating an unbounded payload.
  • Capability stock-pages-v2 is required, preventing mixed-version nodes from endlessly exchanging incompatible stock packets. Pending v1 queries can still receive small v1 responses during upgrades.

Deployment

Update both ES2 and VL4 game servers and the matching client mods to Create-Distant-Stock-0.3.62+mc1.21.1.jar. Continue to use Transerver 0.1.1 on both game servers and the separate Router. Preserve node identity, world data, join codes, configs, escrow and durable queues; do not delete old inbox/outbox/dead-letter files.

  1. VL4: check /distantstock network reports at least one local Create warehouse, not just a network name. Enroll an existing local warehouse from the terminal's picker if needed.
  2. ES2: join the VL4 network code with a portable terminal; select the actual VL4 warehouse and allow the bounded stock pages to populate.
  3. ES2: create a receiving address in the joined network, attach a powered receiving Distant Dock, then send a small test order. Compare /distantstock doctor, /distantstock stock, parcel traces and receipt status on both servers.

Verification and limits

  • 298/298 required GameTests passed, including an actual local Create network enrollment/announcement regression, 5,000 stock rows across bounded pages and client chunks, receiving address scope, delayed join confirmation and duplicate-safe receipt handling.
  • Wire codec, sender, ownership, assets and focused verification tasks passed.
  • Also launched two real NeoForge dev servers attached to an independent Transerver Router; both recognized each other's protocol and transported control-plane traffic. This dev environment contains thousands of historical queued/dead-letter items and no real player-created formal warehouse, so a real physical ES2/VL4 order and parcel delivery has not yet been validated. Live delivery acceptance should be done after installing the build.
  • Unrelated historical Ponder scene stale-NBT verification issue remains outside this update.

The ZIP includes both mod JARs, SHA-256 checksums and detailed Chinese deployment instructions (UPDATE.md).