PLAY PORKLIKE FREE

The lineage runs back to Rogue (1980), a Unix game drawn in ASCII characters: procedurally generated floors, permadeath, and a name that ended up describing an entire genre. Consoles took a decade to catch up. Sega shipped the first widely played console roguelikes at the start of the '90s — Fatal Labyrinth on the Genesis and Dragon Crystal on the Game Gear — and then Chunsoft made the genre respectable in Japan with Torneko no Daibōken (Super Famicom, 1993), which dropped a Dragon Quest merchant into a randomised dungeon, and Shiren the Wanderer (1995), still one of the most admired roguelikes ever built. The defining traits were eventually codified in 2008 as the Berlin Interpretation, by which point everyone already knew them in their hands.

The genre fits weak hardware unusually well, which is why it thrives on my Game Boy shelf. Turn-based means nothing computes until you act — an 8-bit CPU gets a whole turn to think. Procedural generation means a few kilobytes of code outlast megabytes of authored levels. And grid-based dungeons map exactly onto tile-based graphics hardware. Porklike is a modern homebrew entry in a tradition older than the machine it runs on.

The shelf below is not random. Each cartridge answers a different version of the itch Porklike scratches.

Adjustris is the same bargain in falling-block form: a system that refuses to stay still — the well itself adjusts — so no two games settle into the same shape. If Porklike's draw is imposing order on randomness, this is that, at speed.

Tobu Tobu Girl is the opposite pole. Porklike gives you unlimited time per decision; this fast arcade climber — double-jump, dash, stomp upward after a runaway cat — gives you none. For when you want execution instead of deliberation.

Libbet & the Magic Floor is the closest cousin in spirit: grid-based, deterministic, every move accountable. But its floors are authored, not dealt — Porklike asks you to survive the unknown; Libbet asks you to perfect the known.

Big2Small trades infinite dungeons for forty-plus hand-crafted spatial puzzles about guiding large animals through shrinking corridors. Finite, polished, solvable — the anti-roguelike, in the best sense.

Shock Lobster keeps the dungeon-crawling pull but plays it as an action-RPG — an electric lobster, aquatic dungeons, NPCs to talk to. Real-time and authored where Porklike is turn-based and rolled.

Gamepads here are detected the moment you press a button — that is not my politeness, it is the spec. The browser Gamepad API deliberately hides connected controllers from every page until you press something on one, a privacy gate that stops sites silently fingerprinting your hardware. After that there are no button events at all: the emulator calls navigator.getGamepads() every frame and reads the state raw. Polling, not listening.

Two practical consequences. If your pad seems dead, press a button; if it is still dead, my gamepad tester shows exactly what the browser sees — including stick drift, where an analog stick reports movement at rest, which is what deadzones exist to mask. Porklike is immune: D-pad and two buttons, digital all the way down. One brand note while you are here — 8BitDo pads boot into different modes (X-input, D-input, Switch) depending on the button combo held at power-on, so strangely mapped buttons usually mean the wrong mode, not a broken pad.

As for latency: browser emulation stacks small delays — emulator frame, browser compositor, your display — that twitch games can feel. A turn-based roguelike is the most latency-proof genre I host. The dungeon advances when you do, and not otherwise.

Permadeath is the genre's signature, inherited from Rogue itself: when you die, the run is gone, and the only thing you keep is what you learned. My emulator, meanwhile, offers save states that snapshot the whole machine and survive page reloads. These two facts are in direct philosophical conflict, and I will not pretend otherwise.

Use save states freely to pause a run and come back later — that is what handheld design was always about, and a 1989 commuter would have paid real money for it. But checkpointing before every door and rewinding every mistake turns Porklike into a different game: a puzzle with infinite retries instead of a gamble with consequences. Roguelikes are tuned for a player who loses runs whole; death is the teaching mechanism, not the failure screen. If you want games designed around retries, the puzzle shelf exists and is excellent. Either way, I store the states. What you do with them is between you and the pig.