Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Thank you for playing our game and for your detailed analysis!

Regarding autosaves and the "back" button, we deliberately chose to omit them. When a game has more complex mechanics and animations, these features become a near-endless source of bugs and issues with the Ren'Py engine.

As for optimization, you're right. We haven't fully figured out the best way to optimize most things yet. This is also compounded by the fact that we targeted an increased resolution of 2640 x 1440 (instead of standard Full HD) from the start, aiming for better quality

(+1)

If you wish to consider asset resolution 

I suggest considering making your assets into vector pieces rather than raster (instead of PNG or WebM, try SVG)

These can be programmatically scaled in resolution so your players can scale it down as low as 144p to as high as 4k hd. I recall there's a phyton extension that allows you to use SVG ang tweak it 

Having a ton of object instances at once no matter the resolution is ram draining (referring to the thoughts synthesis) specially if they are animated individually (I can see them swaying individually)I suggest instead of animating the instances, try the background instead.


Also thank you for hearing me out 

I understand the part why there's no AS and back (they are hell to maintain XD)