Lemma Soft Forums

Basically just ignore anything other than the last of each category (i.e., using Character() ) -- there can be internal differences, but ren'py will do the work of figuring it out for you, and trying to manipulate such things directly is likelier to lead to an error.

Afaik, there's no easy way to do this out of the box. (I could be wrong obvs.) Other than doing it manually, your best bet is probably rolling some custom function to define characters and append them to a data structure (along the lines of https://lemmasoft.renai.us/forums/viewtopic.php?t=29409 - n...

*shrug* Good luck then. It's not a matter of the character definition itself--it's what Remix said. I would imagine it's likely the say screen but it may be something else.

Honestly, why not just run it on 2014 Ren'py? I don't have your files and I can't verify, but that sounds like an instance where ren'py's internal workings have changed enough that they're not working with your old screens. In any case, is there a particular reason you need to be running this on 7.3...

Handling randomization in screens is more of a headache than it's probably worth, tbh. Pulling the randomization OUT of the screen is the easier solution. Didn't run this, but it should work. *shrug* screen choice(items, randomSTYLE==1): # note the keyword argument passed into the screen (or if not ...

All savable variables (including objects) should be declared with default, i.e.:

default Kronos = Timekeeper()

You're not "refreshing" the screen when you use your Function(). You can manually restart the interaction, but AddToSet() and RemoveFromSet() are honestly probably easier... https://www.renpy.org/doc/html/screen_a ... ta-actions

speaker "[myString]"

I haven't tested it, but the error message itself is telling you that the condition needs to be a string.

Indentation requires a colon (:).

Minor errors in either case: the lack of space between the coordinates and action, and the indentation of color needs to under the text rather than under the window.

Yeah, I couldn't really figure it out either. It works either if you put the default outside the screen (so it's a regular variable rather than a screen variable) OR if you use SetDict, but I don't really see why Function and SetDict would differ in how they treat screen variables. Can't really help...

Yeah, that's weird. Don't know what's up. That said, it appears you can bypass the problem by using SetDict, if that's all you needed.

You can find a few by searching the forums for current label, etc. That said, I previously made similar games with the below setup (conceptually) which worked fine for me. default lastscreen = "room1" screen room1: on "show" action SetVariable("lastscreen", "room1") ... imagebuttons etc use navigati...

You're in luck as it's the new year and things have been very slow at work so I am quite bored. Here, a working example of random clicking (you can throw this in a new project and run it). I didn't bother with the timed part because I don't know what you want to do, exactly. That said, you can searc...