Changelog

• 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).

• 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.

• 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.

Revised the clarification for Game requirements item 4.4.1 and updated the example of a game with merge mechanics.

Expanded the A/B testing of icons 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.

• 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.

• 5.1.1.1: do not use gameplay from other games in screenshots.
• 5.1.1.2: ensure that real gameplay occupies at least 70% of each game screenshot.
• 5.1.1.3: ensure that real gameplay occupies at least 70% of the duration of video materials.