My goal for today is to wrap up the tutorial nodes I'm working on in Quoll.

I've been bogged down in this particular bit of the tutorial because it has three parts, two of which require player input, and even has Glitch traveling autonomously twice

and Glitch has to travel and not just be magicked around because this area of the map is generated at run time

but more, with two nodes the player can stall at, I had to test so much stalling responses

including a variant of a response that has a mere 1/39 chance of happening

I'm a bit bummed I had to fix my bug right now by making Glitch move faster than Ada because I found it fun that Ada could actually follow Glitch on the path

I'll also add writing this part, where Glitch is often the direct object in sentences where Glitch has already been introduced in earlier clauses has been the biggest struggle with not using pronouns

My options are either to use Glitch's name as I did in the last sentence, or to refer to something that you'd usually refer to as belonging to Glitch in the general ("follow Glitch along the path" rather than "follow Glitch along their path")

but it's been really fun? the main bits I wrote months ago, but I'm getting to write Glitch being cute when waiting for Ada at the various tutorial stations within just the paragraphs that tell you Glitch is in the current room

My new TODO technique is unstoppable

Like I have a lot of TODOs in my source code so I can just write little bugs and thoughts and questions down to get them out of my head so I can move on.

But as I'm beginning to get into a release cycle, I have the sense that I should start prioritizing TODOs.

At first, this was just so I can add TODOs that I meant to deal with before I made my commit. Then I realized I can go even further.

So... the number of times I say "TODO" is how big a priority that is.

TODO: Whatever, I'll get to it
TODOTODO: Fix this before the next release
TODOTODOTODO: Fix this before committing