Skip to main content

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

Thanks so much, that's really helpful. Just one more thing: with this approach, you need to download the images again every time you update the app, right? Or manually copy the images from assets/cache folder of the old version to the new version.  Would it be possible to make these images persistent somehow so they don't need to be downloaded again? Currently, I have an external pics folder that I "share" among all the version of the game (by modifying the launch.json so the pics folder points to this external folder). It occurs to me that, maybe, the images might be downloaded to the pics folder or, alternatively, the cache folder may be a external one that can be kept from one version to another. 

Thanks in advance! 

Hi @quantumodo,

Thank you for your thoughtful question! We recommend that you manually move the images from the cache folder to your external pics folder. After you’ve done that, simply update the “image_folders” key in your launch.json file to point to your external pics folder path. This should allow it to function as before.

The engine will only download images if they are missing, so you won’t need to worry about re-downloading them unless new images are introduced.

If you have any further questions or need additional assistance, feel free to ask!

Yeah, that should do the trick. I'll do exactly that, thanks. But just out of curiosity, why keeping two different folders (cache and pics) for the images? And would it be possible to modify the location of the cache folder from the launch.json file?

Thanks! 

Hi @quantumodo,

The reason for having two different folders (cache and pics) is that images downloaded from the internet may not always be correct. By initially placing them in the cache folder, we can verify their integrity before moving them to the pics folder for final use.

Unfortunately, the location of the cache folder is hardcoded and cannot be modified. This feature was designed to simplify image management; we released it for those who find installing the image package challenging.

If you have any more questions or suggestions, feel free to reach out!

Fair enough, thanks!