App manifest

[leonfromont]

According to https://itch.io/docs/itch/integrating/manifest.html I generate a manifest by providing a .itch.toml file in the top level directory of my game directory. However I'm on windows and also want to copy a settings.json file to the users %appdata%\gamename directory. Is there a way to do this or is it expected that all content lives in the same directory?

[fasterthanlime]

Hi!

However I'm on windows and also want to copy a settings.json file to the users %appdata%\gamename directory. Is there a way to do this or is it expected that all content lives in the same directory?

I don't really understand the question.

App manifests are uploaded along with the game - they're the same for all players, and they're only really necessary if you want players to be able to launch different things (the game, a level editor, etc.).

Settings are typically created by the game when it's running. It's good to keep them in the same folder as the game so that when folks backup the game and re-import them into itch later, all their saves are there.

We don't have a cloud save system yet, but when we do, I expect it'll work by giving the game a path to store save files, or by having the game specify a save file location relative to the game's base folder.

Does that make sense to you?

[leonfromont]

Thanks. Yes that makes sense. I want to validate the product key when my app starts up. I am under the impression I can only do that by shipping a build using a manifest and butler. The existing code base generates an installer that follows windows guidelines where all code lives in program files (or wherever the user chooses) and anything that might be modified (settings, save game etc) in the users %appdata% directory. I think you are saying that's not how itch apps are expected to work.

[fasterthanlime]

I want to validate the product key when my app starts up

Before you go down that road, I would really recommend investing elsewhere the effort you'd spend on implementing a form of DRM. A better application will go a long way towards making more revenue, rather than potentially locking up legitimate customers!

I think you are saying that's not how itch apps are expected to work.

Right now there's no guidelines on where to store save files / settings. Some games go with %APPDATA%, some games go with the install folder. I know Windows recommends the former, but the latter does have some benefits because it essentially means they're "portable applications" - and that's the scenario the itch app handles the best.

[leonfromont]

Hi again, Thanks for all you help. RE the DRM I'm just following the guide here https://itch.io/docs/itch/integrating/api/ (the part that says proof of purchase) Are you saying your API will lock up legitimate customers? Is there a different way I should be going about this?

[fasterthanlime]

Are you saying your API will lock up legitimate customers?

Not our API per se, but:

• It'll make it harder for legitimate customers to use your software without using the itch app (maybe they don't like it?)
• It'll make it harder for legitimate customers to use your software offline (why should they need to be connected? maybe they're in a train, or a plane)

Is there a different way I should be going about this?

I would recommend not doing any form of DRM at all. The API is useful if you want to provide online features for your application (multiplayer games, etc.).