btw, I’d like to chime in, I think rare events are bad design for a VN made in ren’py by a one person team.
I didn’t think to say anything but when a game writes let’s say randomscene1 randomscene2 and randomresultnothinghappens3 and then 1=1 2=2 and 3,4,5,6,7,8,9,10 all =3?
I just edit the code to change the 10 to like a 4or5.
If I’m skipping previously seen content with the skip button might as well show me all the content equally (I’m counting the nearly blank even as a full event because it might change depending on factors.)
It’s not just you, most games do this, and I edit them in this same way usually. Why have a slim chance to see any content? ever for any reason?
I get that you write 3 options you want all 3 to appear, but why make one super rare and another super common?
Also rarity is causing bugs via typos:
if selfiechoice < 2:
if selfiechoice == 1:
scene gymselfie0201
with Dissolve(1.0)
e "Let's take a progress pic!"
a "Okay!"
e "Mmm, you're looking tubby in this one, coach."
a "Not as tubby as you!"
else:
scene gymselfie0202
with Dissolve(1.0)
e "Take pic of me posing here."
a "What for?"
e "Just for the record."
a "What record?"
If a number is less than 2 it will always be 1, so else will literally never trigger.
<= 2
or
< 3
Both work fine here, but if you weren’t trying to manage rarity and every time there were X choices you did rand(1,X) you wouldn’t generate this sort of typo so much.
Another similar typo.
When choosing a number between 1 and 2 I don’t think 0 can be chosen?
if Akane.getStage() == 0:
$ image_number = renpy.random.randint(1,2)
if image_number == 0:
scene carboload 01
with Dissolve(1.0)
Should probably read
if image_number == 1:
in the code for visitrin=3 the code is a bit sloppy as you don’t close the if by pairing it with an else. you do
if blah blah blah return more code
it should be if blah blah blah blah else more code blah blah blah return
most of the serious bugs in the untitled demo release of the game were caused by not closing off an if in this fashion, this instance doesn’t appear to cause a bug, but it’s healthier to not use an implied if, it also makes the indentation look neater, and since ren’py is using indentation instead of {} it’s mildly important not to mix it up.
I don’t mean to nitpick and it doesn’t really matter, it’s just odd that sometimes you use a lot of else’s and sometimes you don’t and I think it’s been a source of bugs in the past.
