Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
the user would be plased not have to relocate his save files

Huh? save game locations are to be put into a user specific folder, not the game folder.

You seem to reinvent the wheel a lot.   As a rule of thumb, if no one else is doing something or everyone is doing things a certain way, there usually is a reason. It might be a stupid reason, of course. Or a limitation of some engine.

Like in this thread, the overly big games. The offenders are usually visual novels with heaps of pictures.  If those are lossless output of their rendering chain they are needlessly big and could be made a lot smaller. But here we go back to the reasons why I would not trust a single dev with an updater companion. It is different skills.  Some of the devs are not capable or aware how to make their games reasonably small. Or they just do not care. Or they do, but in a different way. They hear lossy compression and fear for their art to be diminished, or so i imagine.

(2 edits) (+1)
Huh? save game locations are to be put into a user specific folder, not the game folder.

Sorry, I was not clear, the actual save file is in a user local folder, but a huge portion of the game is procedurally generated, thus needs to be cached. Whether I could also save that in a user folder or not is a good question, I think it would be better to not do that so the loading time would be only in the first time anyone runs the game.

limitation of some engine

That's the reason I've seen dev. complaining in another thread in steam, I'm making my own engine so reinventing the wheel some times with more flexibility is a common thing to me.

And yes, I really don't think my game will even be larger than 1GB, as I said most of the data is procedurally generated in the first time you run it, so the actual download size will not be that big.