Lemma Soft Forums

Hmm yea, I have already had some run-ins with call interaction from current context errors. I show my screens and call functions from within them (text buttons are making renpy.call statements), it is part of what is making me query if I am fundamentally misunderstanding how to manage the screen sys...

Howdy, I am looking to make a sandbox game and am looking for some best practices in renpy concerning screens, calling, and best practices for returns and controlling flow. Functionally I want to move around from room to room and interact with characters. Once in a room, the game pauses and waits fo...

Yeah that is the solution I ended up going to - just a couple of label blocks that are instantiating
Plus some checkers in on_load that verify the classes are the same. It seems to hold together fine atm

Yeah, but my understanding is that I can use the after_load label that is auto-executed to verify and pre-check the state of objects. label after_load: #compare class content, rebuild relevant management lists/dicts renpy.block_rollback() With the current Renpy, is that not doable anymore? I feel li...

Hmm ok, I guess I can see why that would be the control flow. Is it considered an acceptable practice then in renpy to call a python block in your starting label to assign all your objects to their relevant default vars? So just have a big old python block statement at the start that sets variables ...

Howdy, I am trying to figure out some of the connectivity stuff between renpy/python and just work out the best way to manage data and persistence. I have a game that stores a ton of its data in lists/dictionaries for easy iteration and access, and most of my characters/types are stored in classes. ...

So I am having a problem with managing screen handling through python, primarily from the issue with contexts. I have a setup where a video runs as a loop and i have an alt angle that can be switched. Using a button to call to cycle the screens. My original solution used label jumping: label first_v...

Ah OK, thanks for those will give it a try, looks like I was misunderstanding how the event handler was operating. Appreciate the multiple alternatives, as a coder I am more interested in understanding how its trying to do things than just have a "use this" response. Thanks.

They are separate images, so the idea is just to have clicking the button swap the images entirely with the images being the entirety of the display (not as part of a BG or composite). So calling them background images that get changed would be a suitable analogy. The main thing I am after though is...

I imagine there is a pretty straight forward way to do this that I am just not getting. Basically I have two images, a zoomed out and zoomed in version and want to have the user click a button to zoom in or out (or hell even a button for zoomed and one for un-zoomed), regardless of the state of the ...