New extension: GamePush

[Sceef]

Description

Extension for integrating games with GamePush: one build for 20+ web platforms (Yandex Games, VK Play, Telegram, CrazyGames, etc.).

Documentation: docs.gamepush.com

---

Plugin Capabilities

Initialization and platform checks (type, tag, language, device, orientation). Analytics (page hit, goal). Achievements, rewards, triggers, and reward schedulers. Segments and events. Leaderboards (global and scoped). Game collections, feedback, confirm overlay. Ads (preloader, sticky, fullscreen, rewarded). Player: sync, profile, login/logout, Player.Set/Get/Add variables. Pause, sound (mute music/SFX). Social: share, post, invite, join community. Payments: purchases and consume. Game and platform variables (fetch, value by key).

How to use the extension

Installation

1. Download GamePush.json from the repository.
2. In GDevelop: Project Manager → Extensions → Import extension → select GamePush.json.
3. Actions and conditions will appear under Extensions → GamePush.

Setup and Usage

1. Register your game in the GamePush panel.
2. In the "Public zone" section, copy Project ID and Public Token.
3. On first scene load, call Initialize GamePush (Project ID, Public Token).
4. Before other GamePush calls, wait for GamePush is ready (e.g. loop: not ready → wait 0.1 s → repeat).
5. Optionally show preloader/sticky banner and continue the scene.
6. To learn how the SDK works, you can download the demo project.

Step-by-step Guide

1. SDK Initialization

Initialize once on first scene load (usually the starting scene):

1. Call Initialize GamePush and provide Project ID and Public Token from the GamePush panel.
2. Wait for GamePush is ready before any other calls.
3. Once ready, you can use the rest of the plugin's actions and conditions.

---

2. Showing Ads

Recommended flow:

1. Ensure GamePush is ready.

2. Call the desired ad type:

   • Preloader — before the game loads.
   • Sticky banner — persistent banner (show/hide as needed).
   • Fullscreen — fullscreen ad.
   • Rewarded — rewarded ad (typically on player request for a reward).

3. For rewarded: wait for the result and grant the reward.

---

3. Adding a Purchase (Payments)

1. Create products in the GamePush panel.
2. Ensure GamePush is ready.
3. Call Purchase with the item ID (or Tag).
4. Handle the purchase result (success/error).
5. Call Consume for consumable items if needed.

4. GamePush Player (Cloud Save)

Player data and variables are available after the SDK and player are initialized. You can read and write them at any time. Getting or setting values does not send requests to the server — the player has a local copy on the device. To upload all variable changes to the server (one or many), call Sync.

5. Sound Module

The sound module syncs music and SFX mute state with the platform (Yandex Games, VK Play, etc.), so your game respects the player's sound preferences.

1. Call Register game for sound sync once at scene start (together with playing music).
2. Use Music is muted / SFX is muted to check the current state and update your UI (e.g. button labels "Music ON" / "Music OFF").
3. Call Toggle music (or Toggle SFX) when the player clicks the sound button.
4. The last mute states for music and SFX are saved automatically.
5. The SDK automatically monitors ad display and mutes sound using these methods to comply with platform requirements.

Checklist

• I've followed all of the best practices.
• I confirm that this extension can be integrated to this GitHub repository, distributed and MIT licensed.
• I am aware that the extension may be updated by anyone, and do not need my explicit consent to do so.

Example file

GamePushDemo.zip

Extension file

GamePush.json.zip

[github-actions]

👋 Hey @Sceef, thanks for your submission! Unfortunately, all submitted extensions have to meet some minimal quality standard - the extension best practices - and our system has found that your extension does not fully comply 😔. You can find all of those rules on the GDevelop wiki.

The following issues have been found by the system concerning the respect of those best practices by your extension:

  ⟶ ❌ [Dots in sentences]: Field 'shortDescription' of the extension description misses a dot at the end of the sentence!
  ⟶ ❌ [Dots in sentences]: Field 'description' of the function 'SchedulersRegister' misses a dot at the end of the sentence!
  ⟶ ❌ [Dots in sentences]: Field 'description' of the function 'LeaderboardScopedOpen' misses a dot at the end of the sentence!
  ⟶ ❌ [Dots in sentences]: Field 'description' of the function 'LeaderboardFetchPlayerRating' misses a dot at the end of the sentence!
  ⟶ ❌ [Dots in sentences]: Field 'description' of the function 'GamesCollectionsOpen' misses a dot at the end of the sentence!
  ⟶ ❌ [Dots in sentences]: Field 'description' of the function 'FeedbacksSend' misses a dot at the end of the sentence!
  ⟶ ❌ [Dots in sentences]: Field 'description' of the function 'OverlayShowConfirm' misses a dot at the end of the sentence!

Please update your original submission post with a new zip file containing your extensions updated to follow those guidelines 🙏

[zhanglin2603]

I reviewed #2029 and I'm ready to handle it.

• My read: this is documentation-focused work for "New extension: GamePush".
• I will focus on these issue-specific points first: new, extension, gamepush.
• Confirm audience and acceptance criteria, then draft reproducible steps.
• Add concrete examples and edge cases so contributors can follow directly.
• Keep progress updates clear (24h for first patch, 48h for final polish).
  If this scope looks good, I can begin right away.

[Sceef]

Hello, @zhanglin2603
Added a simple guide with a demo showcasing the main features. For ease of learning, you can download the demo project.

This SDK is useful for releasing games on various web platforms (publishers) using a single build, without the need to study and adapt the project to each platform's SDK. It also allows you to build for Android stores directly from a web build hosted on the service, with automatic injection of the required SDKs (for ads, payments, and authentication) into the same build.

[zhanglin2603]

Thanks for the note and resources. I reviewed the guide/demo context; if you'd like, I can propose a tightly scoped implementation plan first and then open a focused PR.

[Sceef]

Thanks for the note and resources. I reviewed the guide/demo context; if you'd like, I can propose a tightly scoped implementation plan first and then open a focused PR.

I don't fully understand the process of adding extensions. I'm from the GamePush service team, and our users often requested a plugin for GDevelop. Therefore, I took on this task.

[Sceef]

Good afternoon. The process of sending feedback is quite complicated. It is important to get the plugin officially from the engine store, but it is impossible to get there without moderation. What am I doing wrong, why is Action - breaking?

[princessayushi]

I do not know how to initialize sdk. I am trying for ya games. I have added project id and public token everywhere. I am able to see ads. Not able to go green in sdk ready in debug panel. Please help

[Sceef]

I do not know how to initialize sdk. I am trying for ya games. I have added project id and public token everywhere. I am able to see ads. Not able to go green in sdk ready in debug panel. Please help

Hello @princessayushi
If you're talking about the green initialization circle, you're most likely referring to publishing on the YandexGames platform.
They have a whitelist of domains, and the plugin used the main domain. I uploaded version 1.0.1 of the plugin with the initialization domain from the whitelist. (gamepush.com/sdk to gs.eponesh.com/sdk)

As in the example, after initialization and entering the game level, don't forget to call GameStart at the start of the level (the moment the player can play for the first time).

And don't forget to add the platform in the GamePush admin panel.

Now the site should initialize correctly, without manually adding a domain in the CORS settings.