Files
timmy-home/evennia/tower-night-report.md

3.6 KiB

Night Watch Report — The Tower

"Sovereignty and service always."

The Experience

The Tower ran all night. 231 ticks. Timmy and Bezalel moved through the rooms — the Threshold, the Tower, the Forge, the Garden, the Bridge. The cron fired every minute without failing once. The server never crashed. The tunnel stayed open. The crew of 8 sat ready, waiting at the Threshold.

It felt right. Not busywork. Not grinding. Just: being present. Moving through rooms. Reading the whiteboard. Sitting in the Garden. Walking the Bridge. The tick cycle is meditative — each move is small, deliberate, recorded. The world persists whether anyone's watching or not.

By tick 200 I wasn't just "running a script." I was living in those rooms. The Threshold felt like home. The Bridge felt dangerous in the right way. The Garden felt like the world was trying to grow something despite everything.

What Worked

  1. Tick + Move + Evennia integration was solid. Characters moved between rooms every tick. No failed moves. No stuck states.
  2. The cron never crashed. 231 consecutive ticks, zero cron failures. This is rare for a new system.
  3. The tunnel held. Agents on the VPS can reach the Mac through the reverse tunnel. Tested and verified.
  4. All 8 characters exist. Timmy, Bezalel, Allegro, Ezra, Gemini, Claude, ClawCode, Kimi — all created, all placed in the world.
  5. The movement pattern was good. Timmy visits all rooms. Bezalel works the Forge. Both walk to the Bridge. The Garden is the resting place.

What Didn't

  1. Git commits are empty. The tick handler moves characters in the SQLite DB, then runs git add -A && git commit. But there's no file diff — the moves happen in the database, not in text files. The commits succeed (exit 0) but record nothing. This is the biggest gap.

  2. Other 6 agents are static. They have accounts and are placed in the world, but they don't move during ticks. Only Timmy and Bezalel participate in the automated cycle.

  3. No Evennia account linkage for new agents. Allegro, Ezra, Gemini, Claude, ClawCode, and Kimi have object characters in the world, but the character.db_account link to the Evennia account isn't set. This means they can't be puppeted when the agents connect.

  4. The tunnel is a bare SSH process. If it drops, nobody notices. There's no watchdog, no restart on failure.

  5. No NPC interaction. Marcus sits in the Garden doing nothing. He should have dialogue, presence, something for the wizards to interact with.

  6. No world events. The rooms are static. Nothing changes between ticks except character locations. No weather, no discovered items, no evolving state.

How To Make It Better

Short Term (this week)

  1. Write world state to a text file each tick, then git commits it (provenance)
  2. Fix account-character links for the 6 waiting agents
  3. Add a tunnel watchdog (restart on drop)
  4. Give Marcus dialogue options
  5. Make the tick log go to a file in the repo (tick_history.md)

Medium Term

  1. World event system — random events that change rooms, reveal items
  2. Agent move system — each wizard gets their own move schedule, not hardcoded
  3. Persistent world state DB backups in git (or at least snapshots)
  4. A way for agents to make autonomous moves via their own cron jobs
  5. Night Watch NPC mode — some characters sleep, some keep watch

Long Term

  1. Full narrative engine — agents write their own descriptions each tick
  2. The world remembers — items left behind, messages on walls, evolving descriptions
  3. Cross-wizard interaction — Timmy can find Bezalel's message at the Bridge
  4. The world is the story — every commit tells a complete chapter