Soup: the Game

I went into Soup: the Game expecting a curiosity at best, and came out with a grudging respect for the core idea buried underneath what is, frankly, a very unfinished product. The concept is tight: you control a central mass and spawn units outward to fight rival microorganisms across a top-down battlefield. Fighters actively seek out enemies, mines orbit your mass like defensive moons, and nukes act as guided high-damage missiles you aim at the opponent's weak point. That three-unit toolkit sounds thin on paper, but the moment-to-moment decision of which unit type to commit, and how many to pull back into your core versus push outward, creates real tactical tension in short bursts. Matches run three to five minutes, which means every call matters immediately. The design philosophy here is deliberate constraint. Player input is intentionally minimal, with controls lean enough that two people can share a single keyboard for local multiplayer, which is either a charming party trick or a sign of undercooked design depending on your tolerance for minimalism. For strategy players who want granular build orders and deep tech trees, this is nowhere close. Think of it less like a traditional RTS and more like a real-time tactics puzzle where the complexity lives in the emergent behavior of simple units rather than in menu depth. Whether that emergent complexity actually delivers on its promise is the honest question, and the answer right now is: partially. The rough edges are hard to overlook. At launch there was effectively one map, one AI opponent, and a single achievement that triggered incorrectly regardless of whether you won or lost. Community feedback flagged missing tutorials, a resolution bug that could push the UI off-screen on first launch, and no in-game audio options. The developers have shown signs of active iteration, with Steam community posts referencing new unit behaviors like hunter prowl modes with target-prediction AI, a membrane faction in development, and a rebuilt codebase pushed to a beta branch that reportedly runs cleanly on Windows, Mac, Linux, and Steam Deck. That activity is encouraging, but none of it changes what you actually install from the main depot today. For someone who is genuinely curious about micro-scale RTS design and has a friend sitting next to them, there is a rough but real game here. The AI in the current build is reportedly aggressive enough to send newcomers back to the drawing board several times before a first win clicks, which is at least a sign the base loop has some teeth. The third-faction wildcard, a neutral purple army that attacks both sides, adds chaotic pressure that the more patient player can learn to exploit. That is the kind of emergent wrinkle I find interesting. The problem is that none of it is explained in any interactive way, and new players are dropped in cold. Steam reviews sit at a mixed rating from a very small sample, which is about right. Soup: the Game is a proof-of-concept with a legitimate strategic idea at its center that has been in Early Access since 2016. If the developer delivers on the unit variety and tutorial work visible in the community update logs, this could sharpen into something worth revisiting. Right now it asks for patience and a high tolerance for incompleteness in exchange for a few genuinely tense minutes per session. Diego, Scout Team

Be the first to comment on Soup: the Game.