manyeyedhydra
patreon
Update 24th Mar '24
🕑 Added 2024-03-24 14:25:50 +0000 UTCI was a bit concerned by writing speed had got a little slow and scratchy, so indulged in a bit of ChaosWriting to try and get things moving again.
I think that had a positive effect. A stinking cold and some bugs with HoHH 1.5 knocked me around a bit, but I'm trying to force myself back to my usual daily schedule.
To switch things up a bit, I started work on a short story about a everyday lad answering a job advertisement from a sleazy pornographer, which leads him to a flat with five very attractive, very busty Asian girls. It's me, so they're obviously not human, and the pleasures will turn out to be a little dangerous.
I quite enjoyed writing the setup for this one, even if it's gone a little long. It does seem to break cleanly into two parts. I've written the first. Next week I'll probably keep myself open again. I might write the second part, or see if I've unblocked things to get writing either Temptacia or the Artificial Scylla.
The release schedule might be a little 'off' again. I'm on the mini-bosses. Their scenarios are longer and more complex than the regular harlot scenarios, so I ask for a bit of patience here while I get the first ones written.
In the evenings I've been working on HoHH 1.5. I finished testing a few more of the independent harlots (art of them is on the way, as can be seen with the teaser I've added to this). I hit a potentially scary bug, although it might just be a weird feature of Twine.
"if not $variableName" statements seem to work a little differently in Twine than other programming languages. I seemed to be getting a 'true' result even when $variableName was set to false. I think I've run into weirdness like this before, although I think that was some statements being evaluated to 'true' if $variableName had not actually been defined yet. I think this might be one of those weird quirks of Twine where you have to be a little careful as some bits of code don't do what you think they should.
I'll keep an eye open on it for future testing. In this case it was a Bad End trigger to indicate whether some effects should happen on the Bad End passage, which was then not being reset properly on subsequent visits. I pulled the code out and put it in a more central location, which should have been done before.
The testing continues. Another 30 harlots to go, and then I should be able to put out a proper 1.5 demo of all the Tier 1 harlots (with artwork hopefully!).
Thanks for the support.
I think things are going to be a little chaotic while I work on the mini-bosses. I'll try to keep to the regular end-of-month releases, but I suspect these scenarios are big and complex enough that I might drift from the regular schedule.
- manyeyedhydra
Comments
Many-Eyed Hydra
I think that's what happening here. I'm too used to using it as a shortcut to mean either in other languages.
Joshua
I'm not sure if this is true in Twine, but in a lot of programming languages, checking true/false on a variable returns true if the variable exists/is set, and false if not. There's probably a method for string matching like .equals() or == that will behave as you expect.
