A Dream For Aaron

I kept returning to this little oddity not because it demands your attention, but because it quietly insists there is something worth finding inside it. Vidas Salavejus built A Dream For Aaron alone, and that solitude is written all over every corner of the experience - in the handmade surrealism of its premise, in the rough seams between ambition and execution, and in the peculiar warmth that a game this small can still generate when it commits to its own internal logic. The structure is a first-person shooter wrapped in a roguelite dream-runner. Each run pulls from a pool of procedurally selected maps, enemy placements, gun upgrades, and environmental dressing, so no two sessions are laid out identically. Two major biomes carry most of the content: Desert, full of pyramids, mummies, giant scorpions, and Anubi, and Frost, which sends you through mountain passes against yetis, ice witches, and a sea monster that has no business being in a frozen level. A Darkness endgame stage caps each full Dream completion. Deliver that completed Dream to Aaron and new side travelers appear with quests, extra missions unlock, and hidden Arthas medals scattered through levels gate optional challenge rooms. On paper the loop is tidy. In practice it is a scrappy, low-budget FPS where combat feedback and environmental fidelity are clearly the work of one person stretching a small toolkit as far as it will go. That is both the charm and the friction point. Player counts are essentially zero - the concurrent peak tracked by third-party data sites is two active players, ever - and meaningful critical coverage has never materialized. The Steam review pool is tiny and the community is quiet. What community discussion does exist is earnest: players curious about how Dreams are completed, wondering about chicken healing mechanics, asking the developer directly about roadmaps. That kind of small-scale intimacy between creator and audience is genuinely rare, and it does contribute something to the experience if you are the type who finds that texture interesting rather than alarming. Where the game struggles is exactly where a solo FPS from 2018 tends to struggle: visual polish is minimal, gunplay lacks punch, and the session length data from completionist trackers suggests most players see everything the game has to offer in under two hours. The roguelite randomization extends the run count theoretically, but the underlying level geometry and enemy variety are not deep enough to sustain that promise for long stretches. Expect an interesting afternoon, not a hundred-hour obsession. For players who enjoy scrappy, surreal, solo-developer experiments that sit somewhere between arcade shooter and dream-logic explorer, A Dream For Aaron has genuine personality. It is the kind of game that gets passed over entirely because nobody covered it, which is usually my cue to pay closer attention. Manage the scope expectations and there is something sincere in here.

Kai · Scout Team

Indie & narrative

Be the first to comment on A Dream For Aaron.