My last post, Site 3.7.0, a TV Remote Debugged With a Clock, and a Tic-Tac-Toe Model That Beat the Big Ones, went up about 1:20 AM Sunday. This one covers the rest of Sunday, November 15, and the night into Monday. I was away most of Sunday, so the agents kept going on what I had already approved. In the evening I came back to two threads: making Game-Maker games smaller, and a server that was flooding its own logs.
A sign that fits in one block
Last post, the Starters got shared tiled signs. They were readable, but a sentence like “GRAVITY PULLS YOU DOWN” takes a whole row of blocks, and every block is bytes on the disk.
On Sunday I opened the block editor and drew a sign myself. One block, two words: “JUMP” over “OVER”, in letters three pixels wide and five tall. I sent a screenshot and asked for that. It became a 3×5 micro font.

Codex built the font and the plaques around it. Whole words on a line, one thin frame, and a set of small arrows. W, M and N get wider when the line has room, because “Shy ones wander” and “Moths” were hard to read with narrow letters. The big sign font got a fix too: its pixel columns were uneven (2, 2 and 1 pixels wide), and now they are all 2, so “JUMP OVER IT” packs into 4 blocks instead of 5.
When I saw the first ones, I said it: the block signs with microfonts are perfect. This is what DOS games were like. Memory was tight as well as file sizes.

The bigger saving is sharing. When the words are short, many Starters can say the same thing with the same block. I suggested shorter phrases too: “GO TO DOOR” instead of “WALK TO DOOR”, “CLOCK RESETS” instead of “CLOCK RESTARTS ITSELF”, and “TOO SLOW?” with “GO BACK” or “WAIT” in place of two long warnings. The shared set has 87 plaques now. “EXIT” with an arrow is in 59 Starters.

All the Starter signs together came to 9,425 blocks. The plan brings that down to about 1,236. The first three batches are in: 419 sign blocks down to 55, then 790 to 129, then 744 to 94.

Looking at the renders, I asked for two fixes. Signs up on tall sticks looked odd, so posts are only used near the ground and higher plaques float. And in one level you could not get over a block with one tap of the jump, so the walls and coins there moved within reach of one jump. Nobody should need to discover a trick just to get past a sign.
Plain backgrounds pack better
The same evening I asked why the Starters download so much. Most of them are built the same way, so they should be where the size comes down.
The answer was mostly in the pictures. The dirt in the Starter palette was noise, and noise is the worst case for the run-length packing that GIF and the DOS formats lean on. I asked for dirt that works in horizontal lines. It does not have to be flat. I said plain backgrounds it is.

Codex redrew the Starter backgrounds with a banded sky, clean hills and dirt in layers, with fewer colors. The screens at the start and end of each level no longer carry the game’s title, so 1,093 of them are now byte-for-byte the same across Starters, and the site can share them. Title screens keep their lettering. The Starters the site hosts went from 8.1 MB to 4.5 MB, 44% smaller.
A few rules came up that I want kept as this goes on. Palette entry 0 is always black and 255 is transparent, except in background blocks. Characters keep their own colors for outfits, hair and skin tones. And the palette needs a red, a blue and a yellow, because the DOS player searches for the nearest color for its menus, frames and text.
I have more ideas I have not tried yet. If a site only shares common files, games could share one block file and each add their own signs, even if some blocks go unused. Or keep the blocks as an indexed PNG so the patterns compress well and I can see them at a glance. That only looks right if the Starters share base palettes.
Shrinking a game for a 1994 BBS
All of this turned into a new section of the Ultimate Owner’s Guide: how to make a game small enough to upload to a BBS. In 1994 a caller paid in phone time, and at 2400 baud a caller may spend longer fetching your game than playing it.
I asked for the advice I would have wanted then. Use images with repeating horizontal colors. Use fewer colors. Remove comments from the file’s metadata. Avoid animated GIFs. For FLI cartoons, use a global palette and fewer colors. Some of those are claims about how Game-Maker reads its files, so Codex checked each one against the original DOS source before writing it. The section has five figures drawn from real data: color runs, LZW, a ZIP back-reference, three block patterns with their zipped sizes, and a full FLI frame next to a delta frame.
It also has a table for budgeting phone time, at 10 bits per byte:
- 100 KB: 7.1 minutes at 2400 bps, 1.2 minutes at 14,400.
- 500 KB: 35.6 minutes, or 5.9.
- 1 MB: 72.8 minutes, or 12.1.
Sound got a look too. I listened to voice clips at different sample rates. Most are not noticeably different, but some degrade when you go from 11 kHz to 8 kHz.
Play offline, in pieces
In the last post I paused the offline copy because it had become one huge zip. It is back as individual files, in tiers you choose: the core site, the games, feelies and the library, the spoken tour and phone, and hardware and native exports. It downloads four files at a time, checks each one, picks up where it left off and reuses files that have not changed. Your old copy stays until the new one is complete.
I asked to split the games further, so the Games tier is now Starters, Sandbox, Specials, Bizarre and the CD. Specials are a growing collection, and not everyone needs all of them. Before the Starter diet, the splits came to about 8.4 MB for Starters, 17.9 for Sandbox, 10.7 for Bizarre and 12.1 for the CD. This is on the development branch and goes out with the next site release.
Smaller things
- The held jump everywhere. Almost every Starter now jumps the First Steps way: hold Space to rise, let go to steer, and no second jump until you land. Flat levels start the hero on a raised step with the view locked, so the whole sky stays in view after a jump. Lucky Cat 4.1 got the same jump, with its cracked crossings reshaped so one held jump clears them. A handful of Starters kept their old jump on purpose, where the lesson depends on it.
- Stick Man Stars has the held jump too, a longer fork handle, notebook-page openings with a pencil writing each level’s name, and pencil crosshatching around the gates. I like how it has been progressing since the beginning. My next notes: show a star on the title, line the menu up on ruled paper, and make the stick man easier to see on the dark blue title.
- The laser cryptex. I noticed you could reach the note inside without knowing the code. Now the core’s opening faces down onto the base, ridge tabs stop a partial pull while any digit is wrong, and a bridge holds the stack down. A test checks all 10,000 combinations, and only the right one opens it.
The server: two bugs, sent upstream
I spent much of the night with Kaylee’s agent on the Code Jamboree web server, the one that hosts my sites.
The server runs DigitalOcean’s monitoring agent, do-agent, which sends the charts I see in the dashboard. Under CageFS, the system that gives each hosting account its own walled-off view of the files, the agent was flooding the logs with “duplicate metric” errors. I watched it log 18,400 to 28,600 errors every 70 seconds while using 75% to 126% of a CPU. That is the same kind of log flood that took this server down in April, which I wrote about in Death by Metrics. Back then the only safe workaround was to turn the agent’s filesystem collector off, which also took away my disk charts, as I wrote in Unsupported Should Not Mean Blind. A few days later another outage first looked like the agent again, but turned out to be a memory-hungry security scanner (When Security Got Heavy). Those months of flying half blind are why I built HostScope, now called Zogograph. This time I went after the bug itself, and I went about it differently. Before, I worked these problems by copying text back and forth between ChatGPT and a terminal on the server. This time the agent had a direct connection to the server. It could look at many things at high speed, much faster than I could relay them, and it could clone the open-source do-agent repository, make a fix, build it and verify it live on the server.
The cause was small. To skip a disk it had already counted, the agent built a key from each mount, and the key included the mount’s options. CageFS mounts the same folder again with different options, so the agent thought it was new, counted it twice, and the second count was rejected. Every pass. Forever. The fix drops the options from that key. Kubernetes hits the same bug.
With that fixed, the agent finished a clean pass for the first time, and that showed the second bug. CageFS bind-mounts one physical disk into dozens of paths, and the agent reported each path as its own disk: 71 of them, all at 42.9%.

The second fix reports one mount per physical device, keeping the real root mount. The chart went from 71 lines to one disk and its total.

Both are submitted to DigitalOcean: pull request #368 for the duplicate metrics (from issue #367) and pull request #369 for the bind-mount fan-out. The second one includes tests with real Kubernetes path shapes, not just CageFS. A third problem showed up along the way: a build from source with no version tag makes the dashboard act as if no agent is installed, and hides half the charts. That one is not reported yet.
Then the cautious part. DigitalOcean updates the agent by itself every day, and that update could quietly replace a hand-patched copy. So the server runs the stock agent again, with the disk collector turned off, the safe setup from before. An hourly check emails me if the agent’s file ever changes. That email is my signal that DigitalOcean shipped something, and I can check whether it includes the fixes. One permission fix that has nothing to do with either pull request stays: the agent can read disk statistics again.
The traffic spike
The dashboard showed a burst of traffic Sunday at about 11:40 PM: up to 86 Mb/s for about ten minutes. That is by far the biggest in two weeks. The next biggest was 4.5 Mb/s.

I had installed a new antivirus on the server that day, ClamAV, replacing the one I had before. Its first update has to download the whole signature set, a few hundred megabytes, and its scheduled update ran minutes before the burst. That is the best match. One thing does not fit: a download comes in, but the chart labels the burst as going out, so it is not fully closed. Two smaller spikes, at 3:26 and 4:25 Monday morning, are still unexplained. One of them lines up with the agent being restarted, but this chart is measured by DigitalOcean’s own hardware, so restarting the agent cannot cause it.
The memory chart sat at about 40% instead of the usual 20% to 25%. That turned out to be Linux keeping files in cache after a night of builds, not a leak.
The same weekend also cleaned up the server in other ways:
- The Bard of Bizarre site moved into its own hosting account, and so did Code Jamboree. The Bard site’s contact form was tested end to end after the move.
- The old antivirus is fully removed, so an update cannot quietly bring it back.
- My Git server got a security update, and a disk space alarm now emails me before the disk fills.
- An unused file-sharing install is gone.
- The Code Jamboree site’s links no longer scroll sideways on a phone; they wrap.
There was one real mistake. While debugging, the agent stopped and started the web server the raw way instead of with the hosting panel’s own restart, and every site was down for about a minute. The rule now is to always use the panel’s restart.
Honest about what is not tested
- The two do-agent fixes are tested on the server, but production runs the stock agent until DigitalOcean reviews them.
- The traffic spike: ClamAV is the best match, not a proof.
- The offline tiers, the BBS section and the Starter changes are on the development branch, not on the live site yet.
- The rest of the Starter sign batches are still to come.
What’s next
More plaque batches until every Starter is done. Stick Man’s title and menu. Watch both pull requests for comments, and watch for that email.
Credits
- Code, art and checks for Game-Maker: Claude, with Opus 5.5 directing. Codex (GPT-6.1 Sol) built the micro font, the plaque batches, the Starter backgrounds, the offline tiers, the held-jump batches, the BBS section and the cryptex fix. Kaylee’s agent did some of the sign batches.
- The server work and both do-agent fixes: Hermes Agent on Kaylee, running Claude Sonnet 5, from my requests. Claude (Opus 5.5) in Google Chrome read the DigitalOcean charts. I edit and decide.
- The JUMP OVER sign and the feature image are mine, drawn in the Game-Maker editor.
Covers Sunday, November 15, about 1 AM, to Monday, November 16, about 5:30 AM Eastern. Game-Maker goes from 845a54e to 81bda77.
