I’d be interested to hear other people’s opinions on this. Whenever I’ve downloaded a game from say itch.io and it contains a setup.exe, I’ve sadly just not bothered. Honestly I’m not a huge fan of the installer option, mostly because personally I’d rather not have the tool copying files which I’ll have to use effort to track down when I later want to remove it (in my experience bundled uninstallers usually leave some mess lying around too). From what I can tell it all seems to be mostly a free-for-all, which is can be both good or bad.
Thanks a lot for the responses, it’s really useful to see how people are tackling this. Avoiding this problem is the purpose of installers. If they don’t have them, the game simply won’t run. The main reason I would shy away from the simple “zip up the release package” method is because that will only work for your end-users that have your prereqs already. (Note: by default InnoSetup would only help you for making Windows distributions/installers, but something like this could be promising for Mac/Linux > ) It’s a small learning curve, but the results are pretty slick imho. NET Framework) into one neat little installer. Pretty slick.įor non-Steam releases (like Itch.io), at least for your Windows release, it’d probably be a good idea to look into something like InnoSetup (my personal favorite) which can package together your release build and some prereqs (again, like.
Then, in Steamworks, you can tell steam what prerequisites your game needs (.NET Framework versions, for example), and steam will handle them when the user downloads/installs your game. For steam, the build in Steamworks would just be a copy of your release build.
0 kommentar(er)
