Weekly Report Number 117.
Hi everyone.
I'm a bit early with the report this week, because until a short while ago I was counting up everything I've done, and I decided there's no point in putting it off since a few more hours won't change much anyway. So here it is...
This week I ran into some extra delays that I hadn't planned for, because to my surprise, I'm human after all and I can make mistakes.
At one point, I thought I had some things ready in advance, but when I got to the coding stage to integrate the images into the script, I realized I missed a few possibilities (which translates into images).
The problem is funny, stupid, and simple... at a certain point, the MC may or may not have a specific issue, and as a result, his face gets dirty with a very visible stain.
And what does that mean? Extra images showing the normal MC on one hand, and others with the dirty-faced MC.
This was planned beforehand, but I overlooked a few situations and ended up short on images. And then I discovered that one of the animations also had to show that detail and didn't have it. I took care to create all the animations with that detail in mind, quite a while ago, and they all show the angle where the MC doesn't reveal that part of his face. But the moron overlooked one of them and I had to render it again.
Plus, to avoid creating extra animations, I decided to reuse Kaoru's animations from 0.6a... but this idiot also realized later that at that stage I didn't account for the dirty face at all, so I had to render them all over again. It's not about just rendering the face with the stain, because for that to work, it would have to be present the whole time, and that would take way more time than simply rendering full images again, while I sleep.
To keep from dragging this out or confusing you with too many numbers, I won't go into detail about what was done this week, but I will give you the grand total of what's currently in place for version 0.6b.
Current progress:
• Over 5,000 lines of code.
• Over 15,500 words of dialogue. --> Some things are bound to repeat, and it's practically guaranteed that you'll never experience every single combination, but it's all in the game. A major part of it is entirely new dialogue.
• 1,235 new images so far. --> The same that happens with dialogues. It's very unlikely that you can see all the variants and because of that you won't see everything. But if you review the folder of the images of the version, everything's there.
• 11 completely new animations, plus 2 previously existing ones with minor changes. --> Those two are the ones of the MC and Kaoru rendered again, with a slightly different angle than the originals and the stain on the face.
Scenes with total or partial variations (Important scenes. There are others that are different from what was seen in version 0.6a but they weren't counted. For example, the first shot of the women in the back is different from the one in 0.6a, but it wasn't taken into account.):
• Emma and Cassandra: 4
• Cassandra and Sophia: 1
• MC and Ronald: 13
• MC and Mother: 9
• MC and Finn: 4
• MC alone: 3
• Last positions: 8
• First positions: 3
• MC and girls, outcome one: 12
• MC and girls, outcome two: 6
• MC and someone else, men's post finale: 7
Total scenes with total or partial variations: 70 --> I never intended to be "deceptive", so I need to make it clear that a few scenes are short, perhaps 6 or 8 images, and others are quite long, with more than 40 images. There's a whole mix.
Everything listed above has been tested and is functional.
Still remaining:
• 24 women's finish line scenes.
• 2 follow up scenes.
• Interface notification code adjustments.
• Sound implementation and adjustments.
• Final testing.
The thing about scenes with variants, for example, if we take into account the stuff with MC and Ronald, it doesn't mean they're 13 variants of a single scene. They're actually different scenes that involve both of them, some have two variants, others maybe 3 or more. In short, it's just the total of variable scenes with MC and Ronald interacting, in different situations.
Oh. By the way, the Patrons already know, but this post is for everyone. One of those scenes involves the possible death of MC. But it's very hard to get if you don't know what to do, since to reach that point you've to make several previous decisions and it also involves RNG. So most likely you won't even find out, but the possibility exists... and simply by going back it's solved, or loading a saved game xD
The catch. There's always a catch... and I hope nobody gets mad at me. I've miscalculated and I doubt I can manage to have everything ready for this weekend. I'm getting a flat ass from sitting here all day, I do what I can, but it's a lot. Anyway, I'll make a quick post commenting on this if I see on Sunday that I definitely didn't make the deadline I set for myself.
Anyway, it's true that there's not much left, but I've to make sure I don't screw up with the code for the notifications and new lines of information that are revealed in the interface after some scenes. And the final testing, I've to test every single one of the possibilities and several variants again (not every variant, but enough to verify everything with the notifications). These two things are the last complex part of the final stage.
There's two scenes in particular I want to talk about, both of them being variants of what happens after the men's section is over. One involves Kaoru and has a pretty unique tone that I hope those following this story will understand, because it reveals more about MC's personality and quite a few things about Kaoru as well. But it's just one variant, one possibility out of seven.
Another of those seven possibilities is a scene involving Josephine, and it has something unexpected too. Whether you get to see these scenes or not depends on previous choices and a bit of luck. At some point in the future I'll tell you all the steps needed to unlock them, but for a while, when you play this, you'll have to figure it out on your own.
💖💖💖
Comments (8)
If the MC dies, the show must go on 😏. We could play as Emma, Mother, or one of the ugly robot guards ( ͡° ͜ʖ ͡°) . Otherwise, make him immortal in a cheap way, like the essential NPCs in Skyrim 😄🫠.
Mmm... No way, there can only be one chosen one... okay, three. The Highlander guy, Neo, and the guy/girl from Skyrim 🤣
BTW, how do you handle RNG brances when you do playtesting? I would probably code it so that it becomes deterministic under test...but you seem to enjoy the vast amount of combinations so maybe you just keep retrying until you have seen all outcomes...? :-)
Excellent question. No, I'm not going to leave what I need to test up to chance because checking everything would take too long. Variable values are managed by IF statements that verify if the variable has a specific value X to execute a certain action. If value X isn't met, there are further checks down the line with ELSE or new IF statements. All it takes is commenting out the random value of the variable with a # and assigning it a fixed value. I can go through all the values checked by the IFs exactly as I want, and then I just delete the fixed value and uncomment the random value... everything carries on as if nothing happened. You can also do something similar with the Ren'Py developer console, but I prefer the direct method. It's faster for me. To clarify, everything after the # symbol is ignored, it's a comment, which is why I call it commenting. It's mostly used to comment on pieces of code so you don't forget what they did; it's a memory aid for the developer.
When you say "Kaoru and a pretty unique tone" I suddenly got a flashback to my last playthrough. I really loved the interactions between Kaoru and MC, how it is so clear that she has a completely different experience of him, than he has of her (so far)... and it really sent my mind spinning. It's the kind of storytelling that goes on in my head, long after I have stopped playing/reading.
Great to see your love for details at work. I'm sure it will turn out awesome!
👍
Love it, keep up the good work. Like any project that you take on, sometimes it slips due to no fault of your own. The work is great and you do not put out a crappy product just to hit a self imposed deadline. Keep the faith and high quality.
