> For the complete documentation index, see [llms.txt](https://www.size.club/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.size.club/docs/gameplay/boosts-and-rewards.md).

# Boosts and rewards

Each stage has a boost objective. Keep a valid position open and meet the objective to earn points every second.

## Build a boost streak

The longer you meet the objective without interruption, the more points you earn each second:

| Qualifying time   | Points per second |
| ----------------- | ----------------- |
| From the start    | 10                |
| After 60 seconds  | 20                |
| After 120 seconds | 30                |

If you stop meeting the objective, earning stops and the streak resets. You keep the points already earned. Each new stage starts a new streak.

An order waiting to execute does not earn boost points. You must have an open position that meets the objective. No extra minimum position size applies to boosts.

For example, closing a qualifying **Long Position** stops the boost. Reopening starts a new streak.

A full three-minute stage can earn up to 3,600 boost points. The five-stage maximum is 18,000. Starting later leaves less time to earn.

## Boost objectives

Exposure is the value of your open positions. Use the objective displayed in your stage:

| Objective             | Requirement                                                                                                   |
| --------------------- | ------------------------------------------------------------------------------------------------------------- |
| Long / Short Position | Keep an open position in the required direction                                                               |
| Positive Position     | Every open position must show a profit after trading costs                                                    |
| Keep It Small         | Keep positions open with a combined value of no more than 25% of the starting balance                         |
| Use Less Than Half    | Keep positions open with a combined value of no more than 50% of the starting balance                         |
| Lose Less Than 1%     | Keep a position open and lose less than 1% of the starting balance during the stage                           |
| Pick Your Side        | Keep the direction set by your first qualifying entry. Switching direction disqualifies the rest of the stage |
| Steady Size           | Keep the value of your open positions within 20% of its value when you first meet the objective               |

For **Lose Less Than 1%**, stage performance includes changes in open profit or loss and fees. On a $100,000 starting balance, stage net profit or loss must stay above −$1,000.

For **Pick Your Side**, reopening on the same side is allowed. Boost streak rules still apply.

Some objectives require a specific action, such as banking profit or trimming a profitable position. Follow the displayed condition.

## Bank profit

A qualifying close awards 100 points for each new eligible net-profit milestone of 0.5% of the starting balance. On a $100,000 account, each milestone is $500. Banking is capped at 2,000 points per run.

Losses on open positions count when checking whether you reached a profit milestone. Each milestone pays once, even if you close part of a position or recover from a loss.

The **Profit Banked** message shows the banking award. It adds no separate medal points.

## Earn Mission Ace

Meet the stage objective for 60 continuous seconds to earn 100 points. Mission Ace is awarded once per stage, up to 500 points in five stages.

Other medals add no points. Account tasks and XP are covered in [Progress and events](/docs/community/progress-and-events.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.size.club/docs/gameplay/boosts-and-rewards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.