Skip to content

Connecting Plarium Play🔗

MyGames Store is an additional behavior for existing MRGS modules. Therefore, it will be enough to set additional settings during the configuration and initialization of the MRGS SDK in order to change the behavior. On this page, only the main nuances of connection and use will be noted.

Features of delivery of the application to the store🔗

MRGS makes it possible to upload both native assemblies to PlariumPlay (directly to the store and work with their api), and through the MyGames Game Center

To support PlariumPlay, you need to follow a few steps:

When working natively with PlariumPlay:

  • Create an application in MRGS for the Plarium platform, fill in the keys
  • Set in build define "MRGS_PLARIUM_STORE", initialize MRGS with appid/secret from new app

When using PlariumPlay via MyGames:

  • Use an existing application in MRGS for the MyGames platform, fill in the keys for Plarium
  • Set in build define "MRGS_MYGAMES_STORE", initialize MRGS with appid/secret from old app

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.

Module support🔗

Currently available in the Desktop version:

The issue in the GDPR is resolved on the side of the Game Center (hereinafter referred to as GC) MyGames, as well as MyGamesSupport.

MyTracker is only supported for mobile platforms.

Payments🔗

You need to add to MRGS a list of products available for purchase with their descriptions (as MRGSBank downloads products from the MRGS website). After that, you can use the familiar MRGSBank api to download/purchase products.

Authorization🔗

When uploading a build to PlariumPlay in any of the ways, you will have access to Plarium authorization - MRGSAuthenticationPlarium, which implements the interfaces MRGSAuthentication, MRGSAuthenticationSocialNetwork, see the description of the authorization module for more details

Also, if the application is uploaded to Plarium through MyGames, then MyGames authorization will work in this case.

Tracking PlariumTracker🔗

PlariumPlay requires statistics to be sent in a specific format to their servers. Use the MRGSPlariumTracker class to send all kinds of events from the client.

Working with notifications🔗

Both local and standard push notifications are supported, see the description of the MRGSNotifications module for details

Last update: 2023-02-03
Created: 2022-02-07