Connecting Steam🔗

Methods to access the Steam and Plarium platforms

There are two options for accessing the Steam and Plarium platforms:

1. Different applications are created in MRGS with different appIds, different builds are assembled for each store, the game itself is poured directly into the store, the player downloads it. Updates are also posted to the store separately. Statistics separately for each appId. We support this option for both Steam and Plarium.
2. The game is released only in the MyGames Store, and then the MyGamesStore mini-client is uploaded to the Steam/Plarium stores. After that, the user downloads this mini-client, and MyGamesStore is already launched (in Plarium, for example, it is invisible to the user), and downloads the game posted in the MyGames store, launches it, and automatically generates its id based on the player’s id on the platform (at the same time the downside is that since this happens automatically without entering a login / password, synchronization with the main MyGames account is not possible). Accordingly, the MyGames game center itself also updates the game when it is launched, and in Steam / Plarium there is one assembly of the game center, which is not updated. That is, the player does not download the update via Steam / Plarium, but at startup, the GC itself updates the game. In this case, one MRGS appId is used, one assembly, which is uploaded only to the GC, and statistics on logins / launches / payments, etc. will be one, not divided. We separate payments by platform in statistics with this approach.

According to the code on the client, there is no difference between options 1 and 2. Of the advantages of 2 approaches - one assembly is assembled, poured into the GC, and rolled out on all platforms. Of the advantages of approach 1 - native integration into the platform (when working through the GC in other stores, there may be some problems with UX, but the developers quickly fix them), and completely separate statistics.