The UI is designed more with phone screens oriented vertically in mind. The bands on top and bottom are less noticeable in such layout. But even on computer screens it's hardly an issue, imo -- you still get ~80% of the screen for your text. That's far from "blocked".
LowLevelLesser
Well-Known Member
- Feb 8, 2021
- 1,084
- 1,425
I checked out bad ending #1 and it was certainly fitting and kind of poetic. It will be interesting to see bad ending #2 with the whole "refusing to change" bit and how that will be framed.
You don't have permission to view the spoiler content.
Log in or register now.
Last edited:
Hmm looks most of errors with CGs is fixed in 0.21, except for the first masturbation scene.
The game doesn't handle multiple conditions (the last one defined overwrites the previous ones, due to how the underlying container works) and so MC is drawn with both
edit: also, a tiny continuity glitch. MC now gets option to wear sneakers instead of Converses when picking clothes in the morning on Day 11, but the game is hard-coded to act like they're wearing Converse, even if they're not.
edit2: the transition from the end of 0.20 to beginning of 0.21 is a little jarring, because it's basically the same scene happening twice in quick succession:
Perhaps it'd flow better to cut the beginning from the bit after the jump, and start if from the "Close the door" part?
edit3: the stat changes here seem backward
if MC asks to help backstage instead of playing a role, then you'd imagine that's because they're shy and not ready to face the spotlights, not confident..?
edit4: and one more tiny bug
The game doesn't adjust
It may be more practical and less error prone to only ever make changes to the variables which are on the "left" part of their respective meters, and only adjust the values of matching pairs automatically, when the player clicks the
Python:
{ "sourceUrl": "img/CGs/firstMasturbation/chest/chest1.png", "condition": $breastsProg, "requirement": 2 , "condition": $larm, "requirement": 0 },
{ "sourceUrl": "img/CGs/firstMasturbation/chest/chest2.png", "condition": $breastsProg, "requirement": 3 , "condition": $larm, "requirement": 0 },
//...
{ "sourceUrl": "img/CGs/firstMasturbation/chest/chest1.png", "condition": $breastsProg, "requirement": 2 , "condition": $larm, "requirement": 1 },
{ "sourceUrl": "img/CGs/firstMasturbation/chest/chest2.png", "condition": $breastsProg, "requirement": 3 , "condition": $larm, "requirement": 1 },chest1 and chest2, resulting in having medium breasts even if they don't have any, because the larm check is always passed, either with value 0 or 1.edit: also, a tiny continuity glitch. MC now gets option to wear sneakers instead of Converses when picking clothes in the morning on Day 11, but the game is hard-coded to act like they're wearing Converse, even if they're not.
edit2: the transition from the end of 0.20 to beginning of 0.21 is a little jarring, because it's basically the same scene happening twice in quick succession:
Perhaps it'd flow better to cut the beginning from the bit after the jump, and start if from the "Close the door" part?
edit3: the stat changes here seem backward
HTML:
<<elseif $d15bennetplay is 3>>\
<<set $shy to Math.clamp($shy - 10, 0, 100)>>\
<<set $confident to Math.clamp($confident + 10, 0, 100)>>\
@@.player;"Honestly, I think I'd rather help backstage,"@@ you admit.edit4: and one more tiny bug
HTML:
<<elseif $d2serena is 1>>\
<<set $serenaRelo to Math.clamp($serenaRelo + 5, 0, 100)>>\
<<set $acceptance to Math.clamp($acceptance + 5, 0, 100)>>\$resistance accordingly, so after making this choice the sum of values on the meter is 105% for the rest of the game:
It may be more practical and less error prone to only ever make changes to the variables which are on the "left" part of their respective meters, and only adjust the values of matching pairs automatically, when the player clicks the
Stats button. It'd save a bit of work when writing the game's script, too.
Last edited: