Lemma Soft Forums

I don't believe (though I may be wrong) that you can set arbitrary config variables that way.

Does your code work if you replace config.readback_full with persistent.readback_full? (And initialize it in an init block somewhere?)

It looks like you're missing the indentation that Ren'Py uses to mark blocks. Try: menu: "Coffee.": $coffee=True $dracopoints +=1 $blaisepoints +=1 $theo +=1 $harry +=1 "I think I will have some coffee." "Tea.": $tea=True $severuspoints +=1 $kingsleypoints +=1 $nevillepoints+=1 $gregorypoints +=1 "I...

There are three different ways of doing that, none of them "right" or "wrong". One would be to draw everything to the full size of the screen, and then draw the borders over top of it. This is the easiest of the three, but you take a performance hit from it (not a big deal in most VNs, unless you're...

I suggest doing it the way Alex just suggested, rather than mine -- using yoffset means you can use the default center, left, and right transforms if you choose.

(I didn't even think of the offset properties -- I've never had a use for them before now.)

Hm, that worked for me... Have you changed something else? What version of Ren'Py do you use? Actually, it worked for me, too, when I just tried it now. Some quick testing tells me that the problem I'm having had to do with the priority levels of init blocks -- my project was breaking up all the "i...

I think what you want are parallel blocks. More or less: image my image: "my-image.png" parallel: # alpha code goes here. parallel: # bobbing code goes here. As far as the bobbing code, I'd do that by moving the yanchor property - just make sure you use ypos rather than yalign to position the charac...

The way layout is handled in screen language makes perfect sense to me. Unfortunately, while I can code my screens.rpy (well, I usually split it into one file per screen) however I like, about half the time, the code is completely ignored by Ren'Py. (As a quick demonstration: In a brand new project,...