Lemma Soft Forums

That's fair. I didn't think about how it might cause problems with saving and rollback. I'm talking about 20+ instances of a class with sometimes 50+ attributes depending on which of it's methods are run. Which feels like a lot to me, but I may be overthinking it. Even if it is a lot, it's probably ...

Putting something inside a JSON file means using more or equal memory on disk, since you also need to include the JSON structure. JSON is great because it's human readable, but other than that it still has to be loaded eventually. And I wonder if loading on the fly instead of having the data alread...

Weird question maybe, but I'm wondering if it would be worth it to store data in JSON object files as a way to minimize memory usage in my game. See, in order for a specific gameplay function of my game to work right now, I have a pretty big class that stores quite a bit of data relating to each ins...

Make sure there is not a second entry of this config variable, overwriting your own statement. There is a default entry inside <options.rpy> that uses a "dissolve" as an after-load-transition. Delete that or overwrite it inside the file! Ah, that was it. I feel a bit silly for not checkin...

Here is how you have to use each of them: Ok, placing $ _game_menu_screen = None inside a label does work now, but as for after_load_transition, that's exactly how I have it written, and it still dumps me very abruptly and unceremoniously into loaded saves, no transition or anything... I'm not sure...

I can't get config.after_load_transition = fade or $ _game_menu_screen = None to work. It seems like Ren'Py just ignores these completely. I get no transition when loading a save, and it still shows the save menu when right clicking in game.

Am I using these wrong? What gives?

viewports work great for me on 8.2 What happens if you delete this part if ymax is not None: ymaximum ymax The viewport still doesn't work. The only thing that changes is that the frame takes up the entire vertical length of the screen. (which is not what I want, visually.) Doesn't allow for scroll...

At least, I assume it was the last update that broke it, because I haven't changed anything about this viewport setup since before updating, and it was working perfectly fine before, but now it doesn't work at all. A text viewport that, prior to updating to 8.2.1, used to scroll perfectly fine, now ...

I tried that too, unfortunately that also doesn't work. Put something inside the function to determine if it is called to begin with, like a renpy.notify() statement! Huh, strangely after trying this, it's suddenly working, even though the only thing I changed was adding the renpy.notify statement....

Here's my code: config.label_callback = labelCallback still it only autosaves right before a choice. What am I doing wrong? According to the documentation, the correct variable name is config.label_callbacks (plural!) and it also expects a list. config.label_callbacks = [labelCallback] I tried that...

Hello, I'm trying to change the autosave functionality so that it saves at the beginning of each label instead of saving right before each choice. I thought the best way to do this would be through a label callback function, but it doesn't seem to work. Here's my code: init python: def labelCallback...

As long as you understand how persistent data works and what are implications of its use, it is perfectly fine to use it. The main feature of persistent data is: if you set some value in save A, then it will be accessible in save B, and if save B changes it, it will be retroactively changed for sav...

Still need help with this. I really would prefer to avoid abusing persistent data if I can, but I'm starting to think that abusing persistent data may be my only recourse here. If anyone knows any way I could get this working in order to avoid abusing persistent data, I'd love to hear your suggestio...

Ok, I think I've...sort of fixed it. I can already predict a few problems, so I'm probably still going to need some help with this. What I've done for now is get rid of the "menu" save entirely. The reason I had two separate saves to begin with was because, at the end of each chapter, I ha...

I thought maybe I might try replacing Jump(savefilename + "_menu") in the header screen code with: Function(CallRouteMenu,char) and then in an init python block, i defined the following function: def CallRouteMenu(route): menulabel = route + "_menu" renpy.call_in_new_context(menu...