Spectralis devlog #7 — welcome 5.4.0
—Hello again proggers—
5.4.0’s out. This one brought back a feature I’d basically buried, hardened two systems that were still a little too trust-me-bro, and finally let shared play open where it should’ve been opening the whole time. Also touched the docs, which I’m choosing to be proud of.
Cat or dog? .spectralis
print(f”I try to make stu{2f} which {actually_ships} {5.4.0}”)
Okay let’s get into it~
—Yap—
Big one this round is stories coming back into .spectralis capsules, except not as the thing they used to be — modernized, closer to how album worlds work now, as a proper custom HTML page with real hooks instead of whatever they were before. Rest of the release was hardening and cleanup: Streamer Queue and Discord got a pass to make sure live use doesn’t fall over, shared play finally opens in-app, and the docs stopped lying about what the app actually does.
bringing back a feature I killed is a personality trait at this point
—The Great Suffering—
1 — Stories Are Back, But Not The Same Stories
Old stories concept is back inside .spectralis capsules, rebuilt to match how album worlds work now instead of resurrecting the original implementation as-is. Each one’s a custom HTML page with real hooks into the player — starting tracks, track control, the works — instead of being a static bolt-on. Bringing it back meant actually integrating it with the current architecture, not just copy-pasting the old version back in.
2 — Streamer Queue + Discord Got Hardened
Both of these existed and mostly worked, which is different from “survives actually being used live by a streamer with chat moving.” Went through and hardened the interaction between Streamer Queue and the Discord bot — the stuff that only shows up under real load or real edge cases instead of a clean local test run.
“mostly works” is doing a lot of lifting in software
3 — Shared Play Opens In App Now
Shared play used to need you to go find it. Now there’s an actual open-in-app implementation, so joining a shared room is a real in-app flow instead of a workaround. Small change on paper, but it’s the difference between a feature people use and a feature people forget exists.
4 — Docs, README, and STANDARDS Actually Match Reality
Updated the docs, README, and STANDARDS to reflect what’s actually in the app at this point instead of an earlier version of it. Boring work, necessary work, the kind of thing that only gets noticed when it’s wrong.
—FAQ (no one asked these but they are here)—
Q: What is a “progger”?
A: A human programmer. You. The one who buried a feature and then dug it back up two versions later.
Q: Why bring stories back instead of leaving them dead?
A: Because the concept was good, the old implementation just wasn’t, and album worlds proved the modernized version of the idea actually works.
Q: What counts as “hardening” for Streamer Queue and Discord?
A: The stuff that only breaks under real conditions — live chat, real timing, real edge cases — not the happy path you get testing solo.
Q: Does shared play opening in-app change how sessions work?
A: No, same sessions, same presence/reactions/queue from devlog #6. Just a real entry point now instead of a workaround.
Q: Anything left over for next time?
A: Always. This is a devlog series, not a finish line.
—This is the end*—
*end for now, capsule hooks permitting
再见!!!