How does your game bring our theme, Systems Offline, to life?
In Brownout the city's systems are the game's own systems. A storm keeps knocking out four parts of the grid, and each one runs part of what you play with. When Street Lights fail, the screen goes dark and you see by your headlamp. When Traffic Signals fail, the lights blink yellow, cars stop braking for you and intersections pile up. When Radio + Map fails, your minimap, waypoint arrows and dispatch calls go dead and the HUD glitches, so you're left with a handheld fault tracer that beeps faster as you get closer. When Hospital Power fails, the city's stability drains twice as fast.

The soundtrack works the same way. It's split into four layers, one per system, and a layer cuts out when its system goes down, so you can hear what's broken. Leave a system down too long and it overloads and takes another one with it. At sunrise your shift report is written as patch notes.

What did you do to ensure accessibility of the game?
- Assist mode (title or pause menu): fewer faults, slower stability drain and no cascading failures, so anyone can reach sunrise.
- A "reduced flashing + shake" option that tones down lightning flashes and screen shake.
- Every system has a colour, a letter (L/T/C/H) and a name everywhere it appears, so nothing depends on colour alone.
- Audio cues always come with a visual one: the fault tracer shows signal bars, distance, direction and warmer/colder alongside its beep.
- Repairs are a short arrow sequence with no time limit. A wrong press only steps you back one input.
- Keyboard (WASD or arrows) or mouse in the menus, a How to Play page, mute at any time with M, and pause at any time with Esc or P.
- Runs in the browser with no install.

Did you include the Indieformer or Patch Notes logo somewhere in your game?

If AI was used in your game, let us know how you used it.
I used Claude (Anthropic) in order to better debug code. This is listed in the games publishing as well.