I was considering working on something else, except no, my need for quoll is too high right now
From what I saw last night, I have about 200 nodes to work through due to the premises board change
podcast time again, baby
OK, that's the premise board implemented.
Next up is pulling in some of my responses to solving the first exercise from my Scrivener file.
But I think it's butt break time.
When I start work on Monday, I'll probably just switch my desk to standing instead of taking video game breaks.
But honestly, I think taking a break to do something else is an important part of getting things done.
I got my first bit of writing in and hee-hee my writing is fun
OK, I'm still not at a point where I can check it in, but the first response block congratulating the Playerr and Ada for solving the first puzzle is in and looking good, and I have written some locale paragraphs, but haven't expanded my tests to test them yet.
Lots of little formatting and reformatting. Pretty much the first thing I have to do after copying in from Scrivener is search and replace all the smart quotes and ellipses. I actually have a little sticky note so I can type the alt code to type them into my vscode neovim integration.
From then, it's just a lot of vimmery.
So while testing my locale paragraphs, I made a slight mistake with the level of indentation of one of my rules, and thus I stopped all processing of Glitch as a entity to be described.
One of the more... tricky things about Inform 7 I've found is that it can be hard to tell when you need to explicitly make sure to continue or stop processing of the Rulebook or Activity. This generally bites me in the tail when I write these locale paragraph rules that can be used to remove objects from being described as part of the room description, and when I describe objects in response to "EXAMINE" commands.
This second one is tougher, because I need to not only make sure to stop processing before the default examination reporting rules begin but also not stop processing before the various rules that manage setting the examined object as seen and familiar run.
This is part of the reason why I want to write a style guide because I feel like that would be a good place to collect warnings on such little headaches.