Flukz — open-source shmup community resource open-source GPL devlog  ·  about
// indie shmup & game-dev resource

Game Dev · July 6, 2026

HUD Layout for Bullet-Hell Shmups: Keeping Score and Lives Out of the Danger Zone

In most genres a cluttered HUD is a readability annoyance. In a bullet-hell shmup it is a fairness bug: any HUD element covering the playfield is a patch of screen where the player cannot see an incoming bullet. Layout decisions here have gameplay consequences, not just aesthetic ones.

Start from a constraint most other genres do not have: the entire playfield must remain visible and unobstructed at all times, because the player is reading bullet positions continuously, not glancing at the screen occasionally. That reframes the HUD problem from "how do I fit information attractively" to "how do I display information using zero pixels of playfield space."

Side gutters are your friend

The cleanest solution, and the one most vertical shmups converge on, is to place the playfield in the center of the screen and put all HUD elements — score, lives, bombs, power level, boss health — in the gutters on either side. This works especially well in tate-oriented games, where the narrow vertical field already leaves wide horizontal margins on a standard monitor that would otherwise sit empty. Rather than treating those margins as wasted space to be filled with logo art, use them for information the player needs but does not need to look at directly, since peripheral vision picks up gross changes (a life icon disappearing, a bomb counter dropping) without requiring the player's gaze to leave the action.

Yoko games have a harder version of this problem because the field is already wide and the natural gutters are the top and bottom strips, which are thin. The common solution is a semi-transparent strip along the very top or bottom edge, thin enough that it does not meaningfully cut into vertical dodge room but wide enough to hold single-line text.

What needs to be glanceable vs. peripheral

Not all HUD information has the same urgency. Score updates constantly but the player rarely needs to read the exact number in the middle of a bullet pattern — it only matters at the end of a stage or run, so it can be small and low-contrast. Lives and bombs, by contrast, are decision-relevant in the moment: a player deciding whether to risk a graze for score needs to know, without looking away, how many bombs they have in reserve as a safety net. Give these a distinct color and a consistent screen position so the information reaches the player through peripheral vision rather than requiring a direct glance.

Boss health is the trickiest case because it demands more attention than a life counter but still cannot occupy playfield space. A horizontal bar along the very top of the screen, segmented by boss phase, is close to universal in the genre for good reason: it sits above the action, communicates progress at a glance through fill level rather than requiring numeric reading, and the segment breaks double as implicit phase-transition warnings, which pairs naturally with whatever hitbox design choices you have made for how forgiving phase transitions should feel.

Font and contrast choices

HUD text needs to be legible at a glance against a busy, constantly changing background, which rules out thin fonts and low-contrast color choices that might look fine in a static UI mockup. A heavy weight, a dark outline or drop shadow, and a color that does not appear in your bullet or background palette are the three cheapest wins here. If your bullets are ever red, do not make your HUD text red — the player's eye is trained to react to that color as a threat, and reusing it for score numbers creates a low-grade false alarm every time the number updates.

Handling different aspect ratios and window sizes

If your game supports resizable windows or multiple resolutions, anchor HUD elements to the screen edges rather than to fixed pixel coordinates, and test your layout at both the narrowest and widest aspect ratios you intend to support. A HUD that looks balanced at 16:9 can end up either crowding the playfield or floating awkwardly far from it at ultrawide or narrow tate ratios if it was built and only ever tested at one resolution.

Prototype your HUD with real bullet patterns running behind it, not a static screenshot. A layout that looks clean in a mockup can still turn out to visually compete with bullets once everything is moving, and the only way to catch that is to look at it in motion, ideally during the same passes where you are tuning bullet density and pattern spacing.