Lemma Soft Forums

Eh... I mean, that's a data structure question and basically only you can decide, but if you don't want to change the static item definitions, you could just have a list/dictionary in the screen to keep track (i.e., toppings = {0:[True, False], 1:[False, False]} etc. with True/False switches for eac...

Probably simplest route would be to use a ConditionSwitch or LayeredImage with conditions for the toppings in place of the LiveComposite.

Merely linking because I remember seeing this discussion but did not actually try any of it: viewtopic.php?p=558474

The whole thing seems wildly overengineered, tbh. define mc = DynamicCharacter("mc_name") default names = ["Eisley","Romi","Arianwen","Elvira","Belphoebe","Etol","Aralueni","Morag","Ottoline","Ve...

Use Return() instead of Hide().

https://www.renpy.org/doc/html/screens.html

More documentation on what Ocelot says above. More specifically, anything you want to happen in a screen should be a ScreenAction (e.g., SetVariable rather than directly manipulating a variable).

Nope. It works.

Doesn't auto advance already do this?

Doesn't look like that would run (for instance, there's no screen variable tickets) but I assume it's down to editing for posting. In any case, here's a simple running counter. default tickets = 0 label start: "Start" $ tickets += 50 show screen running_counter(tickets, 50) pause hide scre...

Last I checked this still works - or at least should provide guidance towards getting where you want. viewtopic.php?t=47205

It's all good, everyone's new at one point. Good luck with your game.

Honestly, I would simply put the game down and go study a python OOP course. Barring that, at least another working example. (e.g., viewtopic.php?t=59747 )

From what I've learned thus far (admittedly not much), the default behavior seems to have the player simply say what the option says verbatim. Not really. In the example in the documentation, "Drink coffee" is the text displayed as a choice. "I drink the coffee, and it's good to the ...

1. Branching dialogue trees, with the ability to remove options once read, return to previous topics, and have in-game variables dependent upon choices made. 2. Objects in the background/room that can be hidden or shown on command (e.g., character images which would transition to the dialogue view ...

First of all, none of that should be in a screen - screens run multiple times for prediction and that will break horrendously. I don't understand what you're trying to do based on your post (in an X/Y Problem sort of way). Can you explain, simply, what you are trying to do? What is the relation betw...