Draoi grows a war mode, and Dice Lock now teaches itself in eight movesDraoi grows a war mode, and Dice Lock now teaches itself in eight moves
October 18, 2026 · Draoi picked up a full team battle mode with real fog of war, and Dice Lock started teaching new players by playing with them instead of lecturing them.Draoi can now host full team battles with real fog of war, and Dice Lock teaches new players by playing with them, not lecturing them.
Draoi gets a second mode: full battles, not just duels
Draoi has run as a one-on-one arena since it started. Today it picked up a second mode: Tuatha Dé against Fomoire, two sides on four lane maps, with a stronghold and a heart to break on each end, three lanes with three towers apiece, a wave of creatures every half minute, and experience for every kill. Any player's draoi can fight for either side, and the match ends when a heart falls or a side reaches the kill target. It shares the arena's engine rather than duplicating it. That is why it arrived in one sitting instead of becoming its own project.
The first version of the war maps drew the halls and the paths but left everything visible, which meant a side's own bots could see straight through fog they were never supposed to see through. A second pass later the same day fixed that: the map is now forest everywhere a path, a clearing, a zone or a home was not deliberately cut, and the forest blocks a draoi, a bolt and a look. Two stone halls on each side have a door at each short end. They can only be seen into from inside, or through that door. Each side's sight is recalculated over the map's grid ten times a second and read by the renderer, the towers, the creatures, the bots and the server's own per-side snapshots, so a bot's knowledge of the board now matches what a human on its side could actually see.
Dice Lock learns to teach itself in eight moves
Dice Lock already had a tutorial: eighteen steps, reachable from a How to play link. The problem it never solved is the player who would never open that link in the first place. Today's fix is a first-open walkthrough that raises a real, scripted Survival board the moment a new player arrives and walks them through eight beats on it: swap two dice, swap into a chain, reroll into a chain, press Reroll and watch a die lock, clear the die beside it to unlock, hold to raise the stack, then play on. It is not a diagram of the game. It is the game, paused and staged so the first eight moves always work out.
Shipping that honestly meant proving each beat actually plays before it reaches anyone. A new check, auditBeats, runs the whole eight-beat sequence through the game's own engine whenever the walkthrough is built, rather than trusting the scripted board by eye. On its first run it caught beat six. The board for that step had one cell typed wrong, which would have left a new player's very first lesson stuck on a move that could not be made. From the outside, a broken tutorial step doesn't read as a tutorial bug. It reads as the game being broken, which is why the check runs before a build ships rather than after a player finds it.
Draoi gets a second way to play: full battles, not just one-on-one duels
Draoi has run as a one-on-one duel since it started. Today it picked up a second mode: two teams, two sides on four different battlefields, each with a home base and a heart to break, three paths with three towers apiece, a wave of monsters every half minute, and points for every kill. Any player can fight for either side, and the match ends when a heart falls or a side scores enough kills. The new mode reuses the same game engine instead of building a separate one from scratch. That is why it was finished in one sitting instead of becoming a project of its own.
The first version of the battlefields drew the walls and paths but left everything visible, which meant each side's computer-controlled players could see straight through fog they were never supposed to see through, the same way a human player on the other side could not. A follow-up fix later the same day corrected that. The map is now thick forest everywhere a path, an open area or a base was not deliberately cleared, and that forest blocks sight and attacks alike. Two stone halls on each side have a door at each short end. They can only be seen into from inside, or through that door. Each side's view of the map is recalculated ten times a second, using a technique called shadowcasting, and it is shared with every part of the game that needs to know what a side can see: the display, the towers, the monsters, and the computer-controlled players. A computer-controlled player's knowledge of the board now matches what a human on its side could actually see.
Dice Lock learns to teach itself in eight moves
Dice Lock already had a tutorial: eighteen steps, reached through a How to play link. The problem that tutorial never solved is the player who would never open that link in the first place. Today's fix is a walkthrough that starts the moment a new player first opens the game. It raises a real game board, set up the same way a normal match would be, and walks the player through eight moves on it: swap two dice, swap dice into a matching group, reroll dice into a matching group, press the reroll button and watch a die lock in place, clear the die next to it to unlock it, hold to stack dice higher, then keep playing normally. It is not a picture of the game or a video showing how it works. It is the actual game, paused and set up so the first eight moves always work the way they are supposed to.
Shipping that honestly meant proving each of the eight moves actually works before it reaches anyone. A new automatic check runs the whole eight-move sequence through the game's own rules every time the walkthrough is rebuilt, rather than trusting that the staged board was typed correctly by eye. On its very first run, that check caught move six. The board set up for that step had one square typed wrong, which would have left a brand new player's very first lesson stuck on a move that could not actually be made. From the outside, a broken tutorial step does not read as a small tutorial bug. It reads as the game itself being broken, which is why this check runs before a new version goes out rather than after a player runs into it.