Candy Box 2

Open the page and you get a number. One candy per second, ticking upward, and two buttons: eat them all, or throw ten on the ground. That’s it. No tutorial, no splash screen, no logo. A newcomer might close the tab. The ones who stay find out they are standing at the entrance of a remarkably generous game shipped as a plain web page.

Candy Box 2 was written in TypeScript by a developer known only by the handle aniwey, a sequel to the original Candy Box that turned an idle counter into a cult object. It is published under the GPLv3, which means the whole thing is readable, forkable, and hostable by anyone with a static web server. The canonical copy lives at candybox2.github.io. There is no publisher, no monetization, no account system, and no telemetry. Progress is stored in the browser’s local storage or exported as a text password that can be pasted anywhere.

Market positioning is a strange phrase to apply to something that has never asked for a cent, but it matters here. The first Candy Box is the acknowledged ancestor of Cookie Clicker and the entire incremental genre that followed. Candy Box 2 is the sequel that took the trick seriously. Instead of a counter with jokes bolted on, it built a full RPG with a world map, a dozen zones, a crafting economy, and an actual ending, then hid all of it behind the same dumb number. Critics at the time got it: PC World told readers to go play it immediately, and Cheerful Ghost stamped it Must Play.

The mobile story is messier. aniwey never shipped a phone version. What appears on the App Store and Google Play is Candybox: Mobile, a third-party port by ezagdev, released August 30, 2024, free, legal under the license, and complete in content, but carrying its own rough edges. This review covers both, because the phone is where many people will now meet the game.

• Progressive disclosure as design philosophy: Every button pressed reveals the next piece of the interface. The game teaches itself by withholding, and the moment the world map appears is a genuine jolt.
• A full ASCII RPG: A rat-infested cellar, a desert, a troll guarding a bridge, a cave full of doors, the platforming descent of the Hole, the sea, a forest, a castle, a lighthouse, a dragon, and hell. Each zone is a side-scrolling text scene with its own enemies and loot.
• Layered progression systems: Weapons and armor from the village shop, potions and grimoire spells brewed at the sorceress’s hut, enchantments, and a plantable lollipop farm that turns the second currency into passive income.
• The squirrel: A riddle-dispensing rodent whose questions reward players who actually read the game’s text. It is the purest expression of the game’s personality.
• Portable saves: Local storage plus a copyable text password. A run can move between machines, browsers, or the mobile port without an account.
• Open source under GPLv3: Read the code, patch it, host it. Mirrors and forks have kept the game alive for years.

The Loop

The core loop is a slow-motion reveal. Candies accumulate. They get spent and a new verb appears. That verb produces a new resource or opens a new place, which produces the next reason to spend candies. Where Cookie Clicker iterates on multipliers until the numbers become meaningless, Candy Box 2 spends its numbers on geography. The village shop sells a world map, and the map reframes the counter as a wallet in an adventure game. That reframing is the whole trick, and it lands because the game never explains it. The realization that candies are money arrives roughly when money is needed.

Combat is automatic. The character walks right through an ASCII scene, hits what it meets, and either survives the screen or dies and gets sent home. What a player controls is preparation: which weapon, which armor, which potions are queued, which spells are ready, whether enough candies have been eaten to raise health. That makes each zone a tuning problem rather than a reflex test. The desert teaches that gear matters. The troll bridge teaches that some fights are gear checks that cannot be cheated. The cave of doors teaches that the map hides more map. By the castle, every attempt is preceded by managing a short build list of potions and enchantments, and the game feels closer to a roguelite planning phase than an idle clicker.

The sorceress’s hut is where the systems interlock. Potions and grimoire spells consume candies and lollipops in bulk, which sends the player back to the farm, which forces a decision about how many lollipops to plant versus spend. The lollipop farm is a well-designed passive system because its yield is visible and its upgrades are objects on the screen, not abstract multipliers on a spreadsheet.

Where It Grinds

Here is the fair criticism. The mid-game asks for patience that borders on rudeness. Certain purchases and enchantments sit behind candy and lollipop totals that take long stretches of idling to accumulate at base rates, and the game offers no sanctioned way to speed that up short of leaving the tab open overnight. The community’s answer has always been to open the developer console, and the GPLv3 license makes that a feature rather than a cheat. But a design that quietly relies on players editing their own save is a design with a pacing problem. The original Candy Box was shorter and stranger. The sequel is longer, more coherent, and a little more predictable, a trade some longtime fans still resent.

The Hole is the other pain point, on any platform. It’s a platforming descent with left and right inputs, dropped into a game that otherwise never asks for timing. On a keyboard it’s a cute detour. On a touchscreen it’s the section people quit on, and the mobile section below returns to that.

Interface and Onboarding

There is no onboarding in the conventional sense, and the game is better for it. The interface is a column of tabs that appears one tab at a time. Nothing has a tooltip. The only help is the text itself, and the text is funny in a dry, specific way that rewards reading every line. The squirrel’s riddles are the sharpest example: the answers are hidden in the game’s own prose and in the kind of trivia a curious player picks up along the way. It’s puzzle design that treats attention as the resource.

Onboarding friction is real for anyone who expects a genre signpost. Shown to someone who has never seen an idle game, Candy Box 2 prompts the question of what to do. The correct answer is “press the button,” and that answer is the point. But it costs the game a share of players right at the start, and it’s part of why the mobile port’s store ratings sit lower than the game deserves.

Save Design

The password save is a quietly smart decision. It’s a block of text, it fits in a chat message, and it makes the game portable between the canonical site, any mirror, and the mobile port. No account, no cloud, no sync failures. For a game whose entire pitch is friction-free discovery, refusing to build a login screen is consistent.

Calling this ASCII art undersells the discipline. Every zone is drawn in monospace characters, and the side-scrolling battle scenes animate by redrawing the text block. The dragon and hell are striking as compositions, and the sea’s scrolling scene shows how much motion can be wrung out of characters. The limitation becomes a style: enemies are legible at a glance, loot has a silhouette, and a text-based game of this scope is light on hardware by design. There’s no asset pipeline and no GPU involved; it should run on almost anything that can open a web page.

The weakness of the aesthetic is density. Text-heavy screens like the sorceress’s hut and the grimoire crowd together, and the fixed-width layout assumes a desktop-class viewport. Shrink it and lines wrap, ASCII figures break, and the tab column fights the content for space. Nothing about the underlying game is heavy. Everything about its layout is fragile.

The intended platform is a desktop browser with a mouse and keyboard. Buttons are large, the tab column has room, and the Hole’s directional inputs map to the keyboard with no fuss. It’s the version against which the game should be judged.

On iOS and Android, the game on offer is Candybox: Mobile, a port published under the ezagdev developer account and credited to Noé Le Philippe. It ships the complete Candy Box 2 in an app wrapper, which is exactly what the license permits. The port’s store rating tells part of the story: 3.2 out of 5 from 15 ratings. Two complaints dominate. First, the left and right controls in the Hole are unreliable on a meaningful share of devices, which turns an optional detour into a hard wall for anyone who wants that zone’s rewards. Second, the layout misbehaves on some iPhones, with clipped text and buttons pushed off the visible area, a direct consequence of the fixed-width ASCII design meeting a narrow viewport. Android reportedly fares somewhat better, though the same layout assumptions apply.

The good news is that the password save works across all of it. Start on a phone, hit the Hole, paste the save into a desktop browser, finish the platforming, paste it back. It’s a workaround, not a fix, but it’s a workaround the original design made possible.

Candy Box 2 has aged well by not depending on anything that can rot. It’s a candy counter that becomes an RPG that becomes a small essay on how much a game can withhold and still be generous. The grind is real, the mobile port is rough where it counts, and the sequel is a shade more predictable than its predecessor — flaws that matter, even if none of them dents the central achievement. Few games in the incremental genre offer a world map worth getting lost in.

We recommend the desktop browser version at the canonical site. The mobile port is the same game with a worse frame around it: serviceable for long idle stretches, but it fails in the one section that demands input precision. Treat the phone as a satellite for the run kept on a computer, and the password save makes that painless.