Wrenhaven is a harbour town in autumn 1986. You’re the “& Co.” at retired Detective Inspector Connie Alibi’s two-desk agency. There are five small crimes, five nights, and one cork board.
Every receipt, phone log, ticket stub, press photo, and witness statement says that someone was somewhere at a certain time. Pin them onto each suspect’s line, and the board measures the walk between them on a real town map. Blue ribbons mean there was time. A red ribbon means a story has just become physically impossible, and somebody, or some clock, is wrong.
The board does the arithmetic. You do the doubting.
Paper beats people
Records are never false, but their clocks can be wrong. Statements can be false, and a lie isn’t proof of guilt. That distinction drives the whole game.
Confront a statement that’s part of a contradiction. If it’s false, the witness admits it and the card is stamped FALSE or MISTAKEN. If it’s true, they stand firm and you lose a badge, and Connie tells you what made their story red. Link two cards that describe the same moment seen on two different clocks. If one clock is trusted, like the telephone exchange, the BBC, the church bells, or the Electricity Board, the other clock’s error is found, and every card it stamped slides to its true time. One receipt moving five minutes can sink an alibi. A link only happens when you mean it: a dragged card has to rest on the other until a LINK tag appears, or you can choose Same moment as… and click the other card.




Unknown-person cards, such as a cash receipt or a figure in a photo, show candidate faces that are crossed out as the records rule people out. Each suspect shows a lock: COVERED if they couldn’t have reached the scene for long enough, OPEN if they could, with different icons so the board reads without colour too. The incident can only be pinned when nothing is contradicting and it fits exactly one line, so a wrong accusation is impossible by construction. Then a brass pawn walks the culprit’s route across the map while the night replays, and the Wrenhaven Gazette prints the front page. Each case awards up to three seals: Clean (no badge lost), Unaided (no hint) and Swift.


Five cases and a daily docket
There are five handcrafted cases on one shared town map. The first three each teach one idea, pinning and contradictions, then clocks and links, then unknown persons and a camera’s date-back clock, and the last two combine them: a crime timed by a wrong clock, and a chain of clocks where one can only be checked once another is mended. Every case is proven airtight by the solver.
Once the second case is closed, the case files offer the Daily Docket: a short case generated for each calendar day, with three of the town’s regulars, a small crime and three stories, proven airtight by the same validator before it’s offered. The last seven days stay in the docket drawer, and Copy result puts a spoiler-free line on the clipboard to send a friend.




Settings and graphics fidelity
Alibi & Co. plays with a mouse, a keyboard alone, a gamepad with its own button names, or touch in the browser build, and the pause menu lists the controls as a two-column table for whichever you’re using. Settings sit in two headed columns: volumes, resolution, fullscreen, text size up to Larger, plain lettering that sets every memo, statement and record in a plain sans instead of typewriter and handwriting, reduced motion, and an optional case timer. Menus rise and grow into place, and every case keeps its own board, so a half-solved case is still there when you come back.
Graphics fidelity has four steps. High is the look the game was built with, with MSAA, soft lamp and window shadows, ambient occlusion, bloom, film grain and colour grading. Ultra draws the picture at 1.5 times the window’s size and scales it down, with high-sample occlusion, high-quality bloom, 64-bit HDR colour, 16× texture filtering and twice the dust. No step draws the board’s text below the window’s resolution, so times stay sharp on Low. On the integrated Radeon it was measured on, a busy board took 1.7 ms on Low and 8.1 ms on Ultra at 1920×1080.
What it’s built with
Everything that decides the game, including the board, case data, town map, and solver, is plain C# in Assets/Scripts/Logic/ with no Unity dependency. Unity 6 renders it, and a .NET console app compiles the same files to check it, so the game and the validator can’t disagree.
Clocks are data. Every card names the clock that timed it, and each clock has a hidden offset. A link between two cards calibrates the untrusted clock, and the board recomputes every card’s true time and walking feasibility in one pass, using all-pairs shortest paths over the town’s street graph.
CaseValidator searches every reachable board state using only legal moves. It checks that each case has exactly one consistent solution, that the solved state can be reached from every state, that every designed contradiction can be discovered, that unknown cards only ever resolve to the right person, and that no state allows a wrong accusation. The build runs it before it packages anything, and it proves a year of generated dockets airtight.
How it was made
Alibi & Co. started with a thorough design and technical plan, and its pillars set the tone: the board does the arithmetic and you do the doubting, paper beats people, everything is a physical object on a lamp-lit desk, every case is provably airtight, and it’s cozy noir rather than grimdark.
The pipeline is procedural from end to end. Blender scripts model and render the props, portraits, press photos, and the town map; the suspects are built from fused ellipsoids, voxel-remeshed and smoothed into one surface. The map is generated from the same town.json the game uses, so its streets match the walking times exactly. Python and NumPy synthesize the score, using Karplus-Strong bass, FM Rhodes, vibraphone, and brushes, along with the foley.
After launch, the game went through twelve rounds of improvements, each run by a fresh AI session and pushed only after its logs were checked. Those rounds added cases 4 and 5, the Daily Docket, gamepad, keyboard-only and touch play, the seals, plain lettering, memos that wait long enough to read, links in two clicks and the fidelity slider. One round found that the self-tests’ long-standing 11 frames per second came from the shared desktop, not the game: in a private, invisible KWin desktop they ran at 52 to 56. Autoplay now plays all five cases and the dockets in the desktop build and in headless Chromium and Firefox.
The trailer recorder pipes raw frames to FFmpeg while the game clock steps exactly one frame at a time, and an audio director logs what every voice plays on each frame so the soundtrack can be rebuilt offline.
On phones and tablets
Phones can’t use the desktop’s texture format, so the browser version used to unpack every texture to full size there. Phones now get a separate copy of the game data with ASTC textures, which took WebGL memory at the title from 235 MB to 89 MB on the iPhone profile. They also start on Low graphics, with the picture capped at twice the density and about 2.6 megapixels. A tab the browser killed makes the next visit start on Low with a short notice.
On a touch-first device, a column of large buttons sits beside the picture: Menu or Back, Notes, Hint, Fit, and Full screen where the browser supports it, replacing the game’s own small buttons. Two fingers pinch-zoom the board, held upright the page asks you to turn your phone, and sound starts on the first tap. The session also fixed a tap that started and ended between two frames being silently lost.
It has only been played in headless test browsers with iPhone, iPad and Android phone profiles so far. A real phone still has to confirm iOS’s memory limit, sound, frame rate, and how the controls feel under a thumb.
Play it
Play it in your browser at nearbycoder.github.io/AlibiAndCo, with all five cases and the Daily Docket, on a desktop or on a phone or tablet held sideways. It’s a WebGL build of about 27 MB, or 30 MB on a phone, starting on Medium graphics on a desktop and Low on a phone, with saves kept in the browser.
Download v0.1.0 from GitHub releases for Linux. That’s the October 4 launch build with the first three cases and none of the improvements above; for the current game on the desktop, build it from source with Unity. Controllers and touch have only been tested with simulated input.
Browse the source on GitHub. GitHub records the repository’s creation on October 4, 2026.