To Eat a God

Saying no to Nulla at the wrong moment in To Eat a God can wipe your save files outright, with no warning screen and no confirmation prompt asking if you’re sure. It’s the kind of consequence most visual novels would never risk, and it’s a large part of why the game keeps coming up in conversations about titles that actually make choices feel dangerous instead of decorative.

The Garden and the Puppet You’re Asked to Play

The premise puts you in control of a gender-neutral puppet, an outside presence sent as a gift into a realm called the Garden. Seven divine Symbols maintain the Garden as a kind of testing ground, and the story’s central rule is blunt about the stakes: the characters around you must never find out that the puppet you’re controlling is connected to something outside their world.

That secrecy mechanic is what separates To Eat a God from a standard dating-sim structure. You’re not just picking dialogue options to raise affection; you’re managing a performance, blending into a role convincingly enough that the Symbols around you never suspect what you actually are. Slipping is possible, and the game gives you real opportunities to break character if you want to see what happens when the mask doesn’t hold.

Because the puppet has no fixed personality of its own beyond what you choose to project, the tension isn’t about winning anyone over in the usual visual-novel sense. It’s about deciding how much of yourself, or how little, you’re willing to reveal to characters who were never supposed to know you were there in the first place.

Unum, Septem, and Nulla

Three of the Garden’s Symbols carry most of the story’s weight, and each one represents a distinct approach to what “divine” means inside this fiction.

• Unum is the childlike sun representative — excitable, unpredictable, and the character most players describe as the emotional entry point into the Garden’s cast.
• Septem is the authoritarian ruler of the group, serious by default but volatile enough that the route built around him shifts tone fast once his control starts slipping.
• Nulla is the void guardian, withdrawn ever since the Garden’s Creator disappeared, and the character most closely tied to the game’s willingness to punish the player directly rather than just the puppet.

Route completionists tend to gravitate toward Septem first simply because his route is frequently recommended as the one that establishes the Garden’s power structure most clearly before the stranger routes complicate it.

Beyond these three, the Garden holds well over a dozen additional secondary characters still being introduced as new content passes release, though Unum, Septem, and Nulla remain the three routes most players start with and the three names that come up first in community discussion.

Four Routes, Fifteen Endings, and the Weight of Every Choice

As of the most recent content pass, To Eat a God is built around four playable routes and more are still being added, with over fifteen confirmed endings spread across them. That scale is backed by roughly 80,000 words of script, more than 350 individual CGs, over 250 character sprites, and more than 40 backgrounds — a genuinely large asset count for a game distributed through itch.io rather than a commercial storefront.

Reaching any given ending isn’t just a matter of picking a favorite Symbol and clicking through their route. An affection system tracks how each character responds to the puppet’s choices, and the secrecy mechanic runs underneath all of it, meaning the same dialogue option can land completely differently depending on how carefully you’ve maintained your cover up to that point.

A full pass through even one route with its variant endings runs an estimated four to six hours, and reaching a meaningful sample of the fifteen-plus endings realistically means replaying key decision points more than once, since several of the routes fork hard enough that a single playthrough can’t surface more than a fraction of what’s written.

The Save File Nobody Warns You About in To Eat a God

Nulla’s route is where the game’s fourth-wall-breaking reputation comes from most directly. Players who reach a specific refusal point with him and choose to say no have reported the game responding by deleting their save data, an outcome documented directly in community comments from players who described the moment as genuinely frightening rather than just a clever gimmick. Players specifically drawn to fourth-wall-breaking horror go looking for Nulla’s route on purpose, aware going in that it behaves differently from the rest of the Garden’s storylines.

1. A player completes Septem’s route first, as many walkthroughs and community threads recommend doing before touching Nulla’s storyline.
2. The same player then moves into Nulla’s route, where his withdrawn, grief-driven personality starts pushing the puppet toward a specific refusal point.
3. Choosing to say no to him at that point triggers the save-wiping consequence, with players describing their save icon vanishing entirely rather than simply reverting to an earlier point.

This is also the answer to one of the most common questions people bring to the game before starting it: no, To Eat a God does not warn you in advance that a route can affect your actual save files, and that lack of warning is precisely the point for a story built around a character who exists outside the Garden’s usual rules.

Reactions to that mechanic split the community fairly evenly. Some players treat it as the single most memorable thing about the whole game, proof that Nulla can reach past the fiction and touch something real. Others find it needlessly punishing in a story already asking players to track three other routes’ worth of choices, particularly anyone who hadn’t backed up a save beforehand and lost real progress over it.

Eighty Thousand Words in Two Languages

Beyond the shock value of the Nulla sequence, the sheer size of the script is what tends to surprise people who go in expecting a shorter itch.io visual novel. At roughly 80,000 words across four routes, finishing even a partial run of the content takes real time, and the writing is supported by bilingual Spanish and English text, with Chinese support listed as planned.

Development has continued in named content passes — an Act 2 and a subsequent Act 2.5 interlude have both been released as distinct updates — which answers another question players ask before committing: the game is still actively being expanded rather than shipped as a finished, static release. That ongoing structure is also why the itch.io comment section stays busy, with an active Discord community trading theories about the Garden’s remaining Symbols between updates.

Spanish-speaking players in particular show up often in the comments, a detail worth flagging for anyone assuming a niche indie visual novel like this one would default to English-only text. Between the language support, the confirmed 16-plus content warnings for violence, gore, and unhealthy relationships, and a scope that keeps growing with each Act, To Eat a God reads less like a finished product and more like a serialized story still being written in front of its audience.

To Eat a God earns its reputation less through jump scares than through the specific dread of not knowing whether the story is still just a story. Nulla’s save-wiping refusal sequence, the Garden’s rule that the puppet must stay hidden from Unum, Septem, and every other Symbol watching, and an ending count still climbing past fifteen all point to the same thing: this is a game that treats player trust as something it’s willing to spend.