Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(2 edits)

This is related to modding.

I've found the "write_hotscreen_save()" function and I use it in my mod after user actions that add/remove time to the lock for example. I try to call it as less as possible.

I get there's a ~5 minutes automatic timer. 

What i've found -and I'm maybe wrong here- is the more I call write_hotscreen_save() manually, the more hotscreen will save automatically. And I'm maybe doing something wrong here, let me know.

For example, if I put a print() in "write_save_dict()" to get a visual notification when Hotscreen saves:

  1. I'll see the print in the console 1 time after entering lock mode and then once every ~5 minutes
  2. If I do call write_hotscreen_save() manually after entering lock mode, I'm not sure but I think it'll print every 5 minutes after each call to write_hotscreen_save(). Indefinitively. So the more I manually save, the more it automatically saves.

Not sure this is intended or not. If not, any way we could have a save function independent from the automatic save in a future update?

Thanks :)


EDIT: wrote `I try to call it as much as possible.` instead of `I try to call it as less as possible.` 🤦‍♂️🥴

(+1)

Ok 👌 , I will modify how the save timer is handled so you can call write_hotscreen_save() manually from a mod.

You're the best :)