A new game, Draois, ships a tutorial and a solo adventure levelA new game, Draois, ships a tutorial and a solo adventure level
October 1, 2026 · Draois, a new spell-dueling arena game, got a tutorial and a solo adventure level today, and reckreation's deploys now report when they silently fall behind.A new spell-dueling game called Draois got a tutorial and a solo level today, and a sports-league app now notices when its website quietly stops updating.
last updated
Draois can now teach you how to play, and let you play alone
Draois is a top-down arena battler: sign three elements and the terrain under your feet can supply the third, so the spell you cast depends partly on where you are standing. Until today it only existed as a sparring match against bots, under the working name Signbound, unregistered anywhere in the fleet this site tracks. Today it got a real name, a repo entry in the fleet's registry, a hand-written card on /projects, and a route through the Cloudflare tunnel that answers at jiolab.dev/draois instead of falling through to the site's own catch-all. None of that is visible in the game itself; what is visible is a TUTORIAL button that walks a new player through eight steps as the character Lugh (move, dash, sign, cast, read the ground, empower, manage cooldowns, drop a dummy), followed by four drills per character once one is picked, each resolvable without another human in the room.
The same day added a full solo mode: one character climbs a thirteen-stretch forest level against ten kinds of creature, two locking clearings, a mid-level boss and an end boss, ending the run after three falls. Both additions needed the game's combat rules to work without an opponent typing on another keyboard, which is also why the bot AI changed: an optional "combos" setting, off by default, makes bots set up a hit before paying it off (pin a target, then land the spell that needs a pinned target) rather than picking whatever scores highest in isolation. A parallel string of balance passes, run against a simulation rather than by feel, cut one spell's damage, raised two others, and reattributed damage that one spell had been crediting to the wrong name.
Reckreation's deploys now say what they actually served
Reckreation's production site ran a build from September 5th for 26 days and 112 commits, every automated check on the machine reporting green the whole time, until a session chasing an unrelated bug happened to notice by eye. Twelve minutes after that got fixed, it happened again at a distance of exactly one commit: a text fix landed, and the site went on serving the old text, because landing a change and deploying it are two separate acts and only one of them had run.
Nothing on the machine could have caught either case. The deploy script's last line wrote a Next.js build id to a file, with a comment claiming "the next run can tell", but nothing read that file, and a build id only answers whether two builds match, not whether the commit just landed is the one now live. The deploy now records the actual commit it served, written after the smoke test so a failed deploy cannot claim a commit it never served, and the next run reports that commit's age and how many commits behind HEAD it is. It reports rather than refuses, on purpose: a deploy is the fix for every stale state this check can describe, so a version that blocks deploys would be blocking its own repair.
Draois can now teach you how to play, and let you play by yourself
Draois is a new game: a top-down arena fight where you combine three elemental signs to cast a spell, and the ground you happen to be standing on can supply one of the three for you, so where you stand changes what you can cast. Until today it only existed as practice matches against computer opponents, under an older working name, and it was not yet tracked anywhere on this site's list of projects. Today it got its real name, an entry in the internal list of projects this site's system keeps, a hand-written card on the projects page, and a working web address that actually reaches the game instead of landing on this site's own front page by mistake. None of that shows up inside the game itself. What does show up is a new TUTORIAL button that walks a first-time player through eight steps as a character named Lugh (move, dash, make a sign, cast, read the ground, strengthen a spell, manage cooldowns, and take down a practice target), followed by four more focused lessons once you pick your actual character, all playable with nobody else around.
The same day also added a full way to play alone: one character climbs a thirteen-stretch forest level, fighting through ten kinds of creature, two gates that lock behind you, a mid-level boss and a final boss, and the run ends after three losses. Both of these needed the game's fight rules to work without a second human typing on another keyboard, which is also why the computer opponent changed: a new optional setting, off unless turned on, makes computer players set up a hit before cashing it in (pin you down, then use the spell that only works on a pinned target) instead of always picking whatever single move scores highest on its own. Alongside that, a run of balance changes, tested against a simulation rather than just by feel, toned down one overpowered spell, strengthened two underused ones, and fixed one spell that had been crediting its damage to the wrong name in the game's own records.
A sports-league tracking app now notices when its website quietly stops updating
Reckreation, an app for tracking matches and standings in a recreational sports league, served a version of its website from September 5th for 26 days and 112 code changes, with every automated check on the machine reporting everything fine the whole time, until someone working on an unrelated problem happened to spot it by eye. Twelve minutes after that got fixed, it happened again, this time just one change later: a small text fix was made, and the website kept showing the old, wrong text, because finishing a code change and actually putting it live on the server are two separate steps, and only one of them had actually run.
Nothing in the system could have caught either case on its own. The last step of the update process wrote down an internal build number, with a note next to it claiming a future check could use it to tell if something was wrong. But nothing ever read that file, and a build number can only say whether two updates are identical, not whether the specific change that was just finished is the one the website is now actually showing people. The update process now records which exact change it put live, written only after a final check passes, so a failed update can never falsely claim credit for a change it did not actually serve. Each later update then reports how old that live change is and how many changes behind it has fallen. It reports this rather than stopping the update outright, on purpose: an update is the only way to fix the exact problem this check looks for, so a version that blocked updates would be blocking its own cure.