We want to publish a demo version (as well as the production version) on Steam to allow users to play a limited version of our game. Both versions should point to the same server environment so demo players can maintain their progress in case they choose to purchase the game later. Also they should be able to play together with friends that might have purchased the game. A demo version on Steam will get its own AppId but it seems currently only one

AppId

is supported in

SteamOptions

. Is it possible to support 2 versions currently? If not, is there any other solution than to modify the MetaplaySDK or roll our own implementation? Many thanks beforehand for any insights into this matter!

SDK currently only supports one AppId. The AppID is needed for two reasons: For Login and for the IAPs. If the demo doesn't need the IAPs, I think we can make this work with only a small tweak to the SDK: In

SocialAuthenticationClaimSteam

. Add new

[MetaMember(3)] public uint AppId;

In

SteamCredentialsProvider

Set in the

new SocialAuthenticationClaimSteam()

the AppId to

SteamUtils.GetAppID().m_AppId

In `SteamOptions`: Add

public int DemoId { get; private set; } = 0;

In SteamWorksApiServive.AuthRequest.Send(): Add a client provided appID

steam.AppId

is is either the

options.AppId

or the DemoId Set the

queryString.Add("appid", steam.AppId)

from the request --- For the future, it definitely makes sense for the SDK to support multiple AppIDs. I would expect in that case we'd make the

SteamOptions.AppId

an array and check all of them. But I cannot promise any timeline for this to be implemented. The workaround listed above is relatively compatible with the this expected future version. The hypothetical new SDK version would be compatible with this

demoId

modification. You might get some conflict when updating SDK version (with

metaplay update sdk

) but those conflicts should be trivial.

Thanks a lot for the quick response Jarkko 🙏 Thats an excellent explanation that I should be able to make work! Cheers