BlocksBeyondTheStars Daily: The Performance Release Ships
Version 0.8.3 landed as a coordinated performance push — three stacked PRs cutting network, GPU, and collision costs — alongside a cluster of browser-specific feedback fixes surfaced by real WebGL testing. Together they mark the release documented in PR #375.
Duration: PT2M21S
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-18T04:01:27Z
- Audio duration: PT2M21S
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 18th, 2026, and this is BlocksBeyondTheStars Daily.
Today's story is version 0.8.3, and it breaks into two clear efforts: a three-part performance overhaul, and a cluster of browser-only bugs that only showed up once real players hit the WebGL build on glitch dot fun.
Start with performance. PR #369 greedy-merges the collider mesh, cutting collision tris and nearly doubling frame times on the heavy test walk — 41 to 48 FPS, with GC pressure down sharply. PR #370 follows by finally letting quality presets control MSAA, HDR, and render scale — Potato and WebGL were quietly running…
The second theme is browser-specific feedback reliability, all closed in PR #380 and #373. F1 for help conflicted with the browser's native help key, so WebGL now uses F2 instead. Locale files load asynchronously on WebGL, which left cached menu screens showing raw keys like "ui dot feedback dot send" instead of…
What to remember: the network protocol bump means server and client versions must stay in lockstep, and the feedback pipeline changes assume release builds carry the crash-report key — dev builds intentionally don't.
That's the briefing. Back tomorrow.