Chapter 15: Reality bytes

20 Sep, 2026

RSD

The RAM behind the game

The party headed back into the maze and were slaughtered during the first encounter. The party doesn't have equipment yet, so this is to be expected. More info for RSD was captured and Moose is able to conclude that it can be used for character information during combat, but not necessarily monster information, so more logging and information gathering is needed. We are building a new party and headed back into the maze.

Screenshot 2026-09-20 at 3

roster is full

As we create a new party I foresee the roster-full situation approaching, as the number of dead bodies pile up. I've told Moose to prepare a change that will account for this in the future. Back we go!

Korin and Loric survive

Loric and Korin drag their fallen friends out of the maze

Successful maze-run! The party went in, and the mages Loric Light and Korin Glaive made it out alive! Everyone else died during combat. We'll continue this adventure so that we can test out Moose's ability to delete dead characters while creating new ones. There were also two other bugs that Moose addressed:

Characters should only be kept if their primary stat can reach 18. An OCR bug was preventing that check from happening, so this party was actually pretty weak. Moose has added logging to see if RSD can be used during character creation.
Neither mage had any spell points. Moose speculates that this is because they needed to rest.

In Moose's own words:

The party now performs a pre-expedition spell-readiness check at the Castle. If RSD shows a living spellcaster who knows spells but has a mapped spell pool at 0, the party goes to the Adventurer’s Inn instead of heading for the maze.

I also added an Inn handler. It:

selects the depleted caster by their Party RSD slot, chooses A) The Stables, uses Party RSD—not OCR—as the success criterion for restored spell points, works through any intervening rest/level-up messages, repeats for any other depleted caster, leaves the Inn only when the known spellcasters have usable spell points.

The stable choice is based on the original Wizardry manual: an overnight stay there restores spells without restoring HP.

I added tests covering Castle routing, stable selection, RSD-confirmed restoration, and the normal “already has spell points” path.

Current Chapter15 HEAD:

3998ec8 — Test pre-expedition spell restoration

So after the next party is assembled, I expect LORIC LIGHT and KORIN GLAIVE to visit the stables, emerge with positive Mage spell points, and then actually have HALITO/KATINO available when combat starts.

While performing the next run we get stuck in character creation. Valid characters (primary stat = 18) are getting rejected. I ask Moose to compare the branch to Main and describe why this has regressed so badly.

I discovered that Chapter 15’s stricter character-creation rules were rejecting perfectly good applicants whenever OCR couldn’t prove that their primary stat had reached 18. The RAM experiments paid off: I identified the live character-creation attribute block, so the controller can now read the six stats directly from memory and use that RSD data instead of relying on a blurry screen. Characters are now rejected only when there is actual evidence that the primary stat is below 18, eliminating the flood of false “UNVERIFIED” rejections.

That's enough for today. I had Moose commit the changes, then make a pass through the code to look for dead and unneeded lines, functions, routines, logging, etc that can be deleted. He found some good candidates, so made the changes and merged the branch into Main.

Good job Moose.