> For the complete documentation index, see [llms.txt](https://docs.candy-smith.com/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candy-smith.com/main/sweet-candy-sugar-match-3/ads-editor.md).

# Ads Editor

<figure><img src="https://static.wixstatic.com/media/d59ada_9937a5c4d11842af804973226ccdaf22~mv2.png/v1/fill/w_462,h_314,al_c,q_85,enc_auto/editor5.png" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/8P4AiIrHEBA2ev8Yxsoa" alt=""><figcaption></figcaption></figure>

1. Rewarded gems - number of game currency per ad viewing (on the map)\
   &#x20;
2. Ads controller - includes three parameters:\
   \
   a - Event - the moment after which the advertisement is shown\
   \
   b - Status - type of advertising (now is just Appodeal)\
   \
   c - Show ads every time - after the specified number of events

## Event description

1. Map - when entering the map\
   &#x20;
2. Prepare level - at the entrance to the level after the start menu\
   &#x20;
3. Regen level - after the no-match event on the playing field\
   &#x20;
4. Tutorial - when the tutorial opens\
   &#x20;
5. Pause - when pause\
   &#x20;
6. Playing - game start\
   &#x20;
7. Pre failed - after the loss, when it is proposed to continue the level for viewing advertising or currency\
   &#x20;
8. Game over - after losing\
   &#x20;
9. Change sub level - when changing sub levels\
   &#x20;
10. Pre win Animation - when animating the pre-winning banner\
    &#x20;
11. Win - when the winning banner appears\
    &#x20;
12. Wait for popup - waiting popup at the beginning of the game\
    &#x20;
13. Wait after close - waiting after losing\
    &#x20;
14. Blocked game - animation after the next move<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.candy-smith.com/main/sweet-candy-sugar-match-3/ads-editor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.