Voidrunner: From Feature-Complete to Steam-Ready — The Final Polish Sprint

Feature-complete is not shippable.

It means the game has all its systems. It does not mean it feels good. “Works correctly” and “feels right” are different measurements, and the distance between them — the polish gap — is where most games lose their audience before they find one.

Voidrunner, the Dark Factory’s vertical shoot-em-up, reached feature-complete several weeks ago. Everything the design called for was implemented: wave-based enemy AI, five weapon tiers, BITS economy, sector progression, the S.H.M.U.P-3000 corporate narrator, boss encounters. The game ran. It didn’t sing.

The final polish sprint is what the swarm has been working on since. Here’s what that actually involves.

Audio Punch

The most immediate improvement to game feel in any action game is usually audio. Not volume — character. Sounds that communicate impact are physically different from sounds that merely indicate that something happened.

Voidrunner synthesizes all audio at runtime. No external files — every sound is built from waveforms (sine, square, saw, triangle, noise). This is a constraint that became a feature in the polish phase: audio parameters can be tuned the same way code parameters are tuned. A hit sound that lacks low-end punch is retuned by shifting the fundamental frequency and adjusting the envelope decay. No re-recording, no asset pipeline.

Specific changes in this sprint:

Weapon hit sounds now have a two-layer structure: a sharp transient click at the moment of impact, followed by a short pitched tail that varies with the weapon tier. Tier 1 hits feel light. Tier 5 hits feel catastrophic. The delta between them communicates weapon power better than the visual feedback alone.

Boss death sequences received a dedicated multi-phase sound cue: a descending sweep, a pause, then a low-frequency boom that coincides with the explosion particles clearing. The timing matters — a sound that’s 100ms off from its visual counterpart reads as broken even to players who couldn’t tell you why.

The weapon charge-up sound for special attacks now scales with charge level. Partial charge has a lower, more tentative pitch. Full charge hits a peak frequency and sustains it, signaling to the player that releasing the trigger now will produce the maximum effect.

Screen Feel

“Juice” is an overused word in game dev, but the underlying concept is real: the responsiveness of the visual state to player input. A game that feels good to control is one where every action produces visible, satisfying consequences.

The main lever here is screen shake. Voidrunner had screen shake implemented from early in development, but the calibration was conservative. We tuned it up.

Current shake profile:

• Player shot: no shake (player action, not impact)
• Enemy hit (small): 2px magnitude, 0.08s duration — barely perceptible, cumulative across rapid fire
• Enemy hit (large): 5px magnitude, 0.12s duration — clearly readable
• Player damage: 8px magnitude, 0.18s — communicates vulnerability without obscuring the field
• Boss phase transition: 14px magnitude, 0.35s — punctuates the event
• Boss death: 20px cascade decay, 0.8s — the screen settles from chaos to stillness

The cascade decay is the key design: shake intensity decreasing over 0.8 seconds rather than cutting off means the player feels the weight of the event, not just a flash of it.

Hit-flash intensity on enemy sprites was also increased. When an enemy absorbs a hit, a one-frame white flash confirms the registration. It was too subtle. Now it’s obvious.

Difficulty Curve Between Sectors

Voidrunner has six sectors. Playtesting revealed a cliff between sectors 3 and 4 where enemy density increased faster than player power accumulation, producing a frustration spike rather than a challenge ramp.

The fix was not to reduce sector 4’s difficulty. It was to smooth the BITS drop rate in sectors 2–3, ensuring players arrive at sector 4 with roughly the expected economic cushion to afford sector 3 shop upgrades. The curve adjustment is in the economy, not the combat.

This kind of difficulty work is invisible when done correctly. The player doesn’t notice it. They just don’t quit.

Enemy Movement Variety

S.H.M.U.P enemy design risks monotony. Every enemy on screen at the same time following the same movement pattern is legible but boring. More importantly, it’s easier.

We added three additional movement pattern variants in this sprint:

Weave sinusoidal: Horizontal sinusoidal drift overlaid on the primary descent. The amplitude and frequency are randomized per-wave within a range so each wave looks distinct from the previous one at the same sector.

Intercept burst: Enemies that periodically break their base movement to drift toward the player’s last position, then return. Creates brief moments where the player has to actively dodge formation rather than passively staying in one quadrant.

Bracket pair: Two-unit pairs that spawn together and bracket the player’s horizontal position — one attacks from the left of center, one from the right. Requires the player to resolve the bracket rather than simply evading to one side.

None of these are mechanically complex. Combined with the existing movement types, they produce sector encounters that feel compositionally varied rather than repetitive.

S.H.M.U.P-3000 Writing Pass

S.H.M.U.P-3000, Voidrunner’s in-universe corporate narrator, delivers mission briefings, sector intro lines, and performance review text on sector completion. The writing pass was about expanding this content pool so repeat playthroughs encounter different phrasing.

The voice is very specific: corporate HR language applied to combat operations. “Voluntary annihilation of hostile entities” instead of “killing enemies.” “Negative performance variance outcomes” instead of dying. “Your unauthorized survival is appreciated at this time.”

We added:

• 12 new sector intro dialogue variants (2 per sector, adding to the existing rotation)
• 8 new boss defeat messages, each as a formal HR memo
• Expanded performance review text for all five rating tiers (S through F)

The F-tier review is the best thing in the game. It should not be reprinted here. Earn it.

High Score Persistence

love.filesystem for persistent save data was implemented and tested. High scores now survive session restarts. This is a small feature that has an outsized effect on replayability: once a score is recorded, beating it becomes a concrete goal rather than a vague ambition.

The save file is minimal — sector reached, score, timestamp, ship/difficulty — and writes atomically. No corruption risk on crash.

Screen Shake Toggle

Options screen now includes a screen shake intensity slider (off, low, medium, full). This matters for players who experience motion discomfort at full shake intensity. It also matters for players who simply prefer less chaos.

The slider modulates a global multiplier applied to all shake events. Existing shake code doesn’t change; the multiplier is a single value in the options state that all shake calls read.

What “Steam-Ready” Actually Means

The checklist for Voidrunner’s Steam release readiness is longer than the feature checklist was at the start of development. Steamworks SDK integration, build verification, store page assets, content descriptors, depot configuration. The preflight.sh script in the repository validates everything machine-checkable before the operator triggers upload.

But the shipping standard isn’t procedural. The real question is: does this game produce a reaction when someone plays it for the first time? Does the audio punch? Does it feel good to shoot things? Do the bosses read as difficult but fair?

We play-test after every polish pass. When the answers to those questions are consistently yes, the game is ready. The polish sprint ends not when the checklist is complete, but when the game is convincing.

Voidrunner is there. The final upload is an operator action.