Random Derpoy

Newbie
Dec 20, 2024
73
25
79
My MC's power is at 54. Girls enthralled: 16, including Hana. Yet I have been thrown back into a loop where I'm having to do the story all over again (ie he's contemplating how to enthral Chika, but he has already done so, and it says so in the list of LIs). I have no idea how to progress. Help would be welcome, thanks.
That must be a bug. Though I don't know how that could've happened unless you're character was bounced back to Act 1. In which case visiting a place like the school should return you to act 2/act 3
 

Random Derpoy

Newbie
Dec 20, 2024
73
25
79
The girls from the hint option is not updating with the current one. Right now I have 22 enthrals. Help please
Yeah I've been so focused on just making progress on the game that any characters post the end of Act 2 have yet to be officially added. And I don't know when I'll add them. Still, if you have questions for certain characters, let me know and I'll answer them.
 
  • Heart
Reactions: csum

Noname5379

Newbie
Mar 14, 2023
91
37
145
for some reason after going into the green hair girl's mind, my game kinda just stops. When ever i go to the school it say " i don't need to go here right now." Also when i click the arrow and click the 1st square my game crashes plus cant sleep. 1764489908016.png Untitled.jpg
 
Last edited:

Random Derpoy

Newbie
Dec 20, 2024
73
25
79
this is also happening to me
You either need to talk with Fiona in the student council room, or, download the latest version of the game that I released a couple days ago which includes some bug fix's along with a new debug tool when you click on the bed which resets the day cycle and should patch being stuck in certain time zones throughout the day.
 

Noname5379

Newbie
Mar 14, 2023
91
37
145
You either need to talk with Fiona in the student council room, or, download the latest version of the game that I released a couple days ago which includes some bug fix's along with a new debug tool when you click on the bed which resets the day cycle and should patch being stuck in certain time zones throughout the day.
Nothing happens
 

vilewe7570

Active Member
Oct 5, 2021
887
1,373
327

Ally drinking hot coco pleased.

Bailey eye gazing

A Mother and Daughter Bonding!

Aisha Cooking S'mores

Hana's shining tree!

Nora's Gifts and Giving

Maimei sitting and eating!

Kaori's cake and loving!

Fiona's Confusion and Understanding!

Mika's Interesting Christmas Cheer!

Chiya's Teddy Bear Cheering!

Everyone's Love and Glee!

Merry Christmas Everybody!
 
Last edited:

apexslide

Newbie
Jun 15, 2019
88
145
207
She shouldn't appear in the class, she should appear in the front entrance. Though if she isn't, you either haven't collected all the girls, or there's a bug from the order you did it all.
So essentially the game is fucked and we have to either wait until you fix it or edit the save and fuck it up further just to progress?
 

BatmanPrime

New Member
Apr 25, 2021
7
5
81
Posting this in case it helps other players/modders, and also so the dev can patch it (in script.rpy).

I found why the branches for alienmeeting == 16 and alienmeeting == 21 don’t fire. In my case, alienonhold was set to 1 at the exact moment the bug happens. Because the script checks alienonhold == 1 BEFORE checking alienmeeting == 16 / 21, Ren’Py hits that condition first and jumps to holdalienthing, never reaching the later elif lines.

To confirm it, I temporarily added this right before the condition block:
Code:
"[alienmeeting] / alienonhold=[alienonhold]"
When the issue happened, it printed alienmeeting=16 (or 21) while alienonhold=1.

Below is the original code and two fixes: a minimal reorder, and a cleaner/optimized rewrite (same logic, just readable).

BEFORE (current logic - 16/21 can get blocked by alienonhold)
Python:
label allystory:
if alienmeeting == 2 or alienmeeting == 3 or alienmeeting == 4 or alienmeeting == 5 or alienmeeting == 12 or alienmeeting == 13 or alienmeeting == 14 or alienmeeting == 15 or alienmeeting == 17 or alienmeeting == 18 or alienmeeting == 19 or alienmeeting == 20 or alienmeeting == 22:
jump alienhangout
elif alienmeeting == 26:
jump alienhangoutnogain
elif alienmeeting == 7 or alienmeeting == 8 or alienmeeting == 9 or alienmeeting == 10:
jump sadalienhangout
elif alienonhold == 1:
jump holdalienthing
elif alienmeeting == 6:
jump allyfirstinteraction
elif alienmeeting == 11:
jump allydisguisereveal
elif alienmeeting == 16:
jump alienconfession
elif alienmeeting == 21:
jump allyfcking
elif alienmeeting == 23:
jump allyswarning
AFTER (minimal fix - give 16/21 priority over alienonhold)
Python:
label allystory:
if alienmeeting == 2 or alienmeeting == 3 or alienmeeting == 4 or alienmeeting == 5 or alienmeeting == 12 or alienmeeting == 13 or alienmeeting == 14 or alienmeeting == 15 or alienmeeting == 17 or alienmeeting == 18 or alienmeeting == 19 or alienmeeting == 20 or alienmeeting == 22:
jump alienhangout
elif alienmeeting == 26:
jump alienhangoutnogain
elif alienmeeting == 7 or alienmeeting == 8 or alienmeeting == 9 or alienmeeting == 10:
jump sadalienhangout

# Fix: handle these before alienonhold
elif alienmeeting == 16:
    jump alienconfession
elif alienmeeting == 21:
    jump allyfcking

elif alienonhold == 1:
    jump holdalienthing
elif alienmeeting == 6:
    jump allyfirstinteraction
elif alienmeeting == 11:
    jump allydisguisereveal
elif alienmeeting == 23:
    jump allyswarning
AFTER (optimized/clean version - same behavior, easier to maintain)
Python:
label allystory:

if alienmeeting in (2, 3, 4, 5, 12, 13, 14, 15, 17, 18, 19, 20, 22):
    jump alienhangout

elif alienmeeting == 26:
    jump alienhangoutnogain

elif alienmeeting in (7, 8, 9, 10):
    jump sadalienhangout

# Fix: these should not be blocked by alienonhold
elif alienmeeting == 16:
    jump alienconfession
elif alienmeeting == 21:
    jump allyfcking

elif alienonhold == 1:
    jump holdalienthing

elif alienmeeting == 6:
    jump allyfirstinteraction
elif alienmeeting == 11:
    jump allydisguisereveal
elif alienmeeting == 23:
    jump allyswarning
If the dev sees this: it looks like alienonhold is staying at 1 in situations where meeting 16/21 is expected to trigger. Either resetting alienonhold earlier (where appropriate) or giving those two meetings priority (as shown above) fixes it.

Hope this helps someone else.
 
Last edited: