Documentation changelog

December
  • June
  • July
  • August
  • September
  • October
  • November
  • December
  • 31.07
    • Introduced a new SDK method to retrieve server time that's independent of client settings and resistant to manipulation and overrides.
    • Supplemented information about who can view the Revenue and Average revenue per daily active user metrics in the Monetization metrics and Roles and access rights sections. By default, only the game owner can view the metrics. To allow other developers on your team to view them, assign them the View income role.
    • Updated the descriptions for the Play time, Players, and Play time per player product metrics. The contribution of new players is now shown by a separate curve in the widgets.
    • Added a notice regarding the need to enable the consumption method in the In-game purchases section (item 1.13.1). Be sure to verify unprocessed purchases even during testing to avoid moderation issues.
    • Expanded requirement 1.10: resizing the window must not affect the correct display of a game.
    • Expanded the clarification for requirement 4.4.1. examples of turn-based (conditional) games now include games with merge mechanics. The examples now include a GIF that illustrates such a game.
  • 17.07

    • Updated requirement 8.2.3.6: added information and examples of cases where in-game text translation isn't required.

    • Expanded requirement 1.10.2: the use of swipe-to-refresh is now prohibited in games.

    • Supplemented the clarification for requirement 4.4.1: ads can be served once the game is loaded on the platform (after gameReadyAPI is triggered).

    • Expanded requirement 1.19 regarding the initialization of the Yandex Games SDK and the use of its methods.

    • Updated the information about connecting to the Yandex Games SDK: changed the path https://yandex.ru/games/sdk/v2 to /sdk.js and added options for setups on the developer's domain. Please follow the specific instructions on the SDK installation and use page for SDK initialization (item 1.19.1).

    • Expanded the Game start page and renamed it to Game Loading and Gameplay Markup.

      • Updated examples in the Game loading section. Calling the ready() method from gameReadyAPI when the user can start playing is now mandatory (item 1.19.2).
      • Added the Gameplay section with new SDK methods for reporting to the platform whether gameplay is active or not. When using GameplayAPI, make sure that you call its methods as described in the documentation (item 1.19.3).
  • 9.07
    • Updated information on conversion metrics: Icon CTR is now divided into Icon CTR in recommendations and Icon CTR in "My games" to eliminate the effect of retention rate on CTR. The new metrics can be used to analyze the results of A/B tests for icons and covers.
  • 3.07
  • 2.07
    • Updated the calibration list for interstitial ads (item 4.4.1). Added examples of when ads can be shown.
    • Removed item 2.11 in favor of item 1.8 in the Game requirements section. For mobile devices, focus on adapting the sizes of in-game elements, buttons, and graphics (item 1.8) rather than on the size of the active field.
  • 28.08

    • Added a calibration list for duplicate games (item 3.6). During duplicate checks, moderators assess a game's mechanics and setting. To be approved, a game must have unique mechanics or a distinct setting compared to other games.

    • Updated requirements:

      • 1.6.1.8: The requirement applies to all operating systems
      • 5.9: The requirement applies to any media content
      • 7.13.4.6: Added proverbs, sayings, and facts to the Reading category.

    • Updated the note in the Monetization in Yandex Games section: ad units generate revenue for viewable impressions.

  • 14.08
    • We added a clarification for requirement 2.9 regarding in-game content duration.
    • Added a clarification for requirement 4.4.1: the delay between a player's action and the ad display must not exceed 1/3 of a second.
    • The documentation is now available in Vietnamese.
  • 25.09
    • Updated the clarification for requirement 1.19:
      • The Game Ready call may take up to 90 seconds to return.
      • If Game Ready isn't integrated, you'll see a red indicator .
      • Moved the loader validation logic into the SDK Initialization section.
    • Updated the clarification for requirement 4.4.1: the maximum delay allowed between a user action and the ad display is 0.33 seconds, or 330 milliseconds.
    • Removed Korean from the list of supported languages.
    • Updated the answer to the question "What conditions affect the revenue from a game?"On the Monetization.
  • 11.09
  • 3.09

    • Revised the clarification for requirement 4.4.1 and updated the example of a game with merge mechanics.

    • Expanded the A/B icon testing section. Now you can:

      • Launch testing for Russian-speaking, international, or the entire catalog audience. To gain the most accurate insights, choose A/B testing for the entire audience.
      • Use the Apply icon and cover for other languages option to speed up the loading of creatives for testing.
      • Based on the test results, select the audience for which you want to apply the experiment (when testing across the entire audience).

      Testing is now limited to a 14-day period. To obtain statistically significant results, run the experiment for at least 7 days.

  • 31.10
    • Changed the maximum length of the field SEO description to 160 characters.
    • Added requirements for desktop devices:
      • 1.6.2.6: do not use system key combinations for control;
      • 1.6.2.7: make sure that interacting with the internal game field does not lead to its selection or opening of the context menu.
    • Abolished requirement points 1.6.1.4 and 4.4.2.
  • 23.10
    • Added instruction for checking the delay before the advertisement for compliance with the requirements.
  • 9.10
    • Updated the Events page: added a section on game_api_pause and game_api_resume, which the platform uses to inform the game to pause or resume gameplay. They help comply with moderation requirements (sections 1.3 and 4.7).
    • Added new monetization metrics for in-game purchases: Paying Share and Average in-app revenue per paying user.
    • Updated the Server Time page.
    • Updated information in the explanation for requirements section 4.4.1: a level is considered long if an adult user spends more than five minutes to complete it without losses.
    • Clarified the wording of requirement section 3.6.
  • 2.10
May
  • January
  • February
  • March
  • April
  • May
  • 28.02
    • Removed outdated information about sound on iOS from the verification method of requirement item 1.3.
  • 25.02
    • Updated requirement item 5.1.1.1: it is prohibited to use gameplay from other games in promotional materials and identical promotional materials in different games.
    • Gathered information about ad monetization on a single page.
  • 21.02
  • 18.02
    • On the Events page, the outdated method onEvent() was replaced with on().
  • 14.02
  • 06.02
    • Clarified information about adding games to the platform:
      • For each new game, create a separate draft with a unique ID.
      • A game can be featured in the New section only once, at its first publication.
    • Replaced the name of the feature-meter scale with Card Completion Progress.
    • Added clarifications to the requirements points:
      • 1.3: when the game page is minimized, the sound from it stops.
      • 1.6: the game does not trigger the system player.
      • 1.12: the game has YAN monetization connected or a refusal of it written in.
  • 28.03
    • Wrote instructions on how to add the SDK to an application developed in TypeScript.
    • Restored information about sound on iOS in the verification methodology of requirement item 1.3.
  • 27.03
    • Collected explanations for requirement items 1.2 and 1.2.1 on the Authorization page.
  • 25.03
  • 21.03
    • Added the Purchase metrics page: purchase statistics can now be viewed through the Yandex Games console.
  • 17.03
    • Clarified that the choice of parameter in ysdk.getPayments() depends on where purchases are processed: on the client side (signed: false) or on the server side (signed: true).
    • Changed requirement section 2.14: the game's language should be determined automatically through the SDK. Subsections have been abolished.
    • Added requirement section 6.9. Information from the abolished subsections 2.14 was moved here: if the game's language can be selected manually, then there is no need to know the current language.
  • 12.03
    • Updated information about the request for access to player data: the dialog box is no longer displayed, and the user specifies permissions in their profile.
  • 10.03
Previous
Feedback