Lemma Soft Forums

Hard to say without either your assets or your code, but in general try looking into align properties (https://www.renpy.org/doc/html/style_properties.html#style-property-yalign) or gutter properties (https://www.renpy.org/doc/html/style_properties.html#style-property-top_gutter). In the case of the...

My bad, that should be a repeating timer.

*shrug* tbh not sure, I don't tend to use Drags() much. That said, I haven't really found any reason to need Drags(), since you can always build the drags programmatically if you need to get data from elsewhere. For example: init python: def rice_dragged(drags, drop): print("rice") def egg...

Ah, yes, I had skimmed the part of the OP that said that. Well, the principle remains the same, I guess, just adjusted to move one "step" at a time and wait before moving to the next step. I would probably use a timer to repeatedly call the function on a small delay. screen repeating_funct...

Use either of the following if checks:

While you CAN use a CDD for finer control, you also don't need it for simple linear movement. (Sidenote: I don't understand how your move_testcar function is supposed to work in the context of the game, but I assume that's due to it being edited for posting here.) init python: def move_testcar(): gl...

The following mostly seems to work. For reference, supplying transforms to a drag using at is not supported even when using screen drags (not Drag()s). Other attributes (like dragged, draggable, etc.) should probably be given in the Drag() definition and not added to the screen directly. screen drag...

Wouldn't renpy.focus_coordinates (https://www.renpy.org/doc/html/other.ht ... oordinates ) be enough to get the info you need?

Note that I am not particularly offering advice on how to best approach this, because that's a complicated question that I am ill equipped to deal with without your assets or your design goals. Simply to answer your specific question: the way you do it now the hotspots would be in a different place,...

If box size is not specified, a box is only as large as it needs to be - i.e., the size of the largest child. While there are many ways to approach organizing your screen, the path of least change for now is probably to specify the xsize of your vbox.

A hotspot needs an action to be hoverable (use NullAction() as a placeholder if need be). You also wouldn't be able to see whether your hotspot is since your idle and hover images are the same. imagemap: ground "flowchart_repaired_no_true" idle Solid("#FF09", xysize=(config.scree...

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...