Brotato Review: How Much Game Can You Fit Inside a Potato?

Official promotional artwork for Brotato, developed and published by Blobfish. Source: official game press kit. Used for review and commentary.

Brotato looks like a joke and plays like a design argument. It is a top-down arena-shooter roguelite about a potato wielding as many as six weapons while trying to survive waves of aliens. The characters are potatoes, the arena is small, the graphics are plain, and the story barely exists. It resembles the sort of premise that should exhaust itself shortly after the first laugh.

Instead, it reveals how little surface complexity a game needs when its decisions remain tightly connected. Weapons, statistics, characters, items, rerolls, money, enemy pressure, and wave timing all operate inside the same compact system. A purchase does not matter only because of what it adds. It matters because it changes the value of what the player already owns and what may become useful later.

That distinction keeps the game from being merely minimalist. Minimalism can produce elegance, but it can also disguise thinness. Brotato feels substantial because its limited components combine productively. The potato joke attracts attention; the shifting logic of the build sustains it.

A Small Loop That Never Stops Asking

The basic loop is easy to explain. Weapons fire automatically by default while the player moves through a confined arena, dodging enemies and collecting materials. A wave ends, the potato gains one or more level-up choices, the shop opens, and the next round begins. Runs are short, and individual waves usually last well under two minutes.

The brevity matters because decisions arrive before the player can settle into complete autopilot. Combat tests the current build; the shop asks what the next version should become. Do you buy the weapon that solves an immediate survival problem or an item whose value depends on several later purchases? Do you repair a weakness, deepen a strength, or spend money rerolling in search of something that may never appear?

The shop therefore functions less like a reward screen than a sequence of commitments. Once a build has begun to favour melee damage, engineering, critical hits, elemental effects, harvesting, luck, armour, dodge, or lifesteal, later offers stop having fixed values. An item that is mediocre in isolation may complete the logic of the run. A powerful item may be irrelevant because it belongs to a different economy.

Randomness keeps those commitments unstable. Shops and level-up options do not reliably provide the piece the player wants, but the game offers several ways to bargain with uncertainty: rerolling, locking an unaffordable item for later, adjusting luck, or choosing a character whose modifiers make particular categories more useful. Chance determines what appears. The player decides how much money, flexibility, and future security to spend responding to it.

That produces a different balance from the more planning-heavy form of roguelite discussed in Across the Obelisk, where persistent systems allow much more of a strategy to be constructed before and around a run. Brotato offers less advance control and compresses adaptation into repeated shop visits. Its question is not whether a perfect plan can be executed, but how long an imperfect plan still deserves confidence.

A deterministic version of the game would become a solved sequence too quickly. A version governed almost entirely by chance would make planning feel cosmetic. Brotato stays between those failures: uncertain enough to force improvisation, but controllable enough that a loss usually exposes a decision rather than merely bad fortune.

Potatoes as Rule Changes

The character roster is the main engine of replayability. Calling them different potatoes sounds ridiculous, but mechanically each is a variation on the rules. One favours particular weapons. Another changes how many can be carried. Some reward a statistic that normally remains secondary, restrict an obvious strategy, or make an apparently poor item unexpectedly valuable.

The characters need little biography because their identities are expressed through constraints. A potato is not memorable because the game tells a story about it. It is memorable because choosing it changes the problem the player is trying to solve.

This gives the same weapons and items multiple lives. A weapon ignored during one run becomes essential in another. A statistical penalty that would usually be unacceptable becomes manageable because the character gains something more valuable in exchange. The game does not need an endless supply of unique mechanics when it can repeatedly change the context in which existing mechanics are judged.

The best runs develop in stages. At first there is only an intention: build around fast melee weapons, turrets, critical hits, harvesting, or some less sensible combination. A few purchases align, and the intention begins to acquire structure. Attack speed compensates for low individual damage; lifesteal turns aggression into recovery; engineering converts empty ground into automated defence; an economic investment delays power now in exchange for more options later.

Then the next wave tests whether the theory was real. A build that looked elegant in the shop may lack the damage to control the arena or the defence to survive contact. Another may appear weak for several waves before its interactions finally connect. The player is not simply accumulating bonuses. The player is making claims about how the numbers will behave under pressure.

Crimsonland After the Roguelite Turn

The older arena shooter Crimsonland was the comparison that first came to mind, partly because I remember playing it as a child. It offers the same direct pleasure of movement, shooting, escalating weapons, tightening enemy pressure, and eventual collapse. Its contract with the player is wonderfully immediate: the screen fills, and you react.

Brotato inherits that arena-shooter tension after several stages of genre evolution. Positioning still matters. A small opening between enemies can decide a wave, and an underpowered build leaves very little room for error. Yet combat execution is only one part of the challenge. The shop, character modifiers, short-run structure, and procedural offers turn survival into the visible consequence of decisions made between rounds.

That difference explains why the action can appear simple while the game remains absorbing. In a more traditional arena shooter, much of the satisfaction comes from aiming, movement, weapon selection, and reflex. Brotato automates much of the firing and places more weight on preparing the conditions under which movement will succeed. The battlefield proves whether the economic and statistical machine was constructed well enough.

Minimalism Without Emptiness

Brotato is visually plain, but not carelessly so. Enemies, weapons, projectiles, materials, and hazards remain readable even when the arena becomes crowded. The art does not compete with the build system for attention, and the game wastes little time asking the player to admire scenery or wait through narrative transitions.

That restraint could have made the production feel cheap. Instead, it makes the game unusually clear about what it wants to be. Many modern games strain to function simultaneously as films, novels, theme parks, social spaces, service platforms, and long-term lifestyle commitments. Brotato is content to be a compact toy in the best sense: a system that becomes more interesting through repeated handling.

The length of a run supports that design. Failure does not erase an evening, and a bad purchase does not require hours before its consequences become visible. The player can lose, reconsider the build, and test a revised idea before frustration hardens into resentment. Short runs do not make failure meaningless; they let the game teach at a higher frequency.

Its machinery is also unusually exposed. When a run collapses, the likely causes are often legible: damage scaled too slowly, defence was postponed too long, the build depended on an item that never arrived, or too much money was spent chasing an ideal shop. The explanation may be incomplete, but it is usually specific enough to produce another theory.

That is the foundation of “one more run.” The next attempt is not merely a repetition of the last. It is an experiment designed to correct it.

Brotato and Vampire Survivors

The obvious comparison is Vampire Survivors. Both belong to the broad family of survival roguelites in which attacks are largely automated while the player dodges enemies, gathers resources, and develops into an increasingly destructive centre of the screen. Their pleasures, however, are arranged differently.

Vampire Survivors often builds towards spectacle. Weapons evolve, effects multiply, and a successful run becomes a fireworks display. The player gradually stops resembling a vulnerable figure surrounded by monsters and becomes something closer to a moving weather system. Compounding power is made gloriously visible.

Brotato is more compressed. The smaller arena, shorter waves, character restrictions, and frequent shops make the shape of the build feel more deliberate. Power still compounds, but the strongest pleasure comes from constructing the economy that produces it: deciding which statistic deserves another increment, which weakness can remain exposed, and whether the next reroll is still an investment rather than desperation.

This gives Brotato an analytical flavour without making it slow. It offers much of the satisfaction of theorycrafting without the overhead of a large role-playing game: no enormous inventory, lengthy campaign, or prerequisite study of lore. There is only a potato, a shop, a wave timer, and a sequence of increasingly consequential bad ideas.

That is how much game can fit inside a potato. Not an infinite quantity of content, but a limited set of rules arranged so that their meanings keep changing. The humour makes the first run inviting. The design ensures that the next one still has a question to ask.