Update 20th April '25

The last couple of weeks I've been struggling trying to get the harlot notebook code right.

What was causing me issues is I'd made a few design mistakes with the architecture, so every time I'd try and check some other clue type, I'd go to reuse existing code only to find out it was corrupting a variable for a subsequent call or missing a required check. It was not a good framework.

I spent Sunday and Monday going through and reorganising it so that there was a clear distinction between function calls (as much as I could mimic function calls in Twine) from the harlot scenarios and the underlying calculations. This cleaned it up and looked much more stable.

I took Tuesday off and then spent Wednesday and Thursday testing it and squashing the many many bugs from various typos and other nonsense.

It looks a lot more stable now and was able to apply it to one of the harlots (Asphya). Her clues are in place, I just need to write up the notebook section so it's not just a bunch of "clue solved" messages.

Since then I've been working through the other harlots and adding autosave while I figure out what information their notebook page should display to the player.

Originally, I was going to try for a weekend release, but rushing was the cause of things going badly wrong a couple of weeks ago. My plan now is to keep working through the harlots, get about three or so done with fully written up notebook sections and put that out Wednesday for people to test.

With that major hurdle out of the way, next week I'll go back to my usual balanced work schedule of writing scenarios in the day, and updating the harlot code in the evening.

Apologies for the delays on this. That was a bit too much hacking away in the code thicket than I anticipated!

- manyeyedhydra