Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

I think it's more complicated than that. Downloading 50Mb at the start of the game is ok if you're on a PC with a reasonably fast internet connection. If you're on a cell phone (which usually has a slower connection), and you have to pay for the amount of data you download, it becomes problematic.

If you expand the game over time and it becomes significantly larger than 50mb, it will take too long to load on a PC too.

If you don't use spritesheets (as RPG maker does in some cases) and don't put thematically similar graphics in sheets, this increases the number of files significantly.

In my opinion, it is difficult to find a sensible solution for what is allowed and what is not. That's why I asked support how strict the 1000 files rule is. The answer was that exceptions to the rule are really exceptions.

As soon as the game reaches a certain size and you have a version 1.0, you should make it downloadable and installable.

Games on Itch are usually not "installable", they are unzip and run.

Commendable that you do use the html5 features for loading on demand. This is why I a voice my bafflement about the restriction. This is not the only thread about this topic.

I have yet to see a good explanation why the number of files indicates a lazy export from a game engine that results in a bad user experience.

Because as I understand it, you did not export this and had a lot of files because of that, but you developed for web directly. Making this explanation "many files = lazy engine export" be rather questionable.

Would not an engine developer quickly learn about such restrictions and have an option to reduce file number, but otherwise be as lazy an export as before?

I would understand it, if it was said that number of files puts strain on the servers or any other explanation. But I do not follow the chain of logic that is currently used. Or that is used as far as I understood the explanations.

In one of those threads the developer tried to pack the files only to find out that the packing method used could not be used over web, because the unpacking method is not allowed for security reasons and only works on a development build on local client. Did not sound like a lazy engine export either.

I do understand the discouragement of lazy engine exports that would work better as a download version. But I question the method of using a file counter as an indicator for this.