BlocksBeyondTheStars Daily: Audit Fixes Ship in v0.7.7
A single audit pull request closed out eight confirmed bugs across the server and Unity client, from trade cargo mismatches to memory leaks, and the fixes are now documented in the v0.7.7 changelog.
Duration: PT2M20S
Episode overview
This episode is a short developer briefing from BlocksBeyondTheStars Daily.
It explains recent repository work in plain language.
- Show: BlocksBeyondTheStars Daily
- Published: 2026-07-14T04:00:57Z
- Audio duration: PT2M20S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's July 14th, 2026, and today's story is one big cleanup effort landing in a single, well-tested pull request.
The headline: PR number 319 closes out eight bugs found during a read-only audit of the server and Unity client, and every single one shipped with a fix verified against the code, not just a patch.
The through-line across these fixes is state isolation — making sure the game reads and writes from the right place. Trade and give-item logic was pulling items from a shared ship cursor instead of each player's own cargo hold, meaning an aboard-ship partner's trade offer could get validated against the wrong…
A second theme is data integrity on save. The block-id palette fix, tied to issue 318, is probably the highest-risk item in the batch: adding new block types could silently remap existing saved data to the wrong blocks. That's now persisted and remapped atomically across both SQLite and Postgres.
On the client side, commit b80204b tackles a steady native-memory leak — chunk meshes weren't being released by Unity on re-mesh or unload, so long sessions would grow memory over time. That's now cleaned up on every chunk destroy path.
Five new regression tests back…