# Game self-check

Use this short checklist before uploading a game. It covers the most common moderation blockers.

**Games are often rejected for the following reasons:**

* The Playgama Bridge SDK is not integrated, the Game Ready event is not sent, or progress is not saved through SDK methods.
* The game is a low-quality title built entirely with generative AI and does not add anything meaningful to the player experience.
* The app interface is not translated into all declared languages, or the interface language does not match the game language.
* Ads are configured incorrectly: they disrupt gameplay, fail to pause sound, or do not grant the promised reward. See the [advertising requirements](/playgama/game-requirements/advertising-requirements.md) for details.
* Sound in the game does not pause when an ad is played or when the screen is minimized.
* The game does not properly save player progress.
* The app contains technical messages or errors, crashes, or freezes.
* The app name does not match between the game and the draft materials in one language.
* The app has bugs or issues that hinder usability.
* Important interface elements are cut off by the game area boundaries (making some actions in the game impossible).
* The game violates copyright laws (names, brand logos, music).
* The game fully or partially copies another game in the catalog.
* The game includes integrated analytics such as Google Analytics (GA4).

The full list of requirements can be found on the following pages.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.playgama.com/playgama/game-requirements/game-self-check.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.