> 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/score.md). # Score Your score determines your rank. It combines trading points, stage boosts, profit banking, and Mission Ace awards. ## Trading points Trading points are based on your net profit or loss from open and closed trades, after trading costs. They can rise or fall. Your score can be negative. Return is measured against the $100,000 starting virtual balance. This calculation always uses the starting balance, even after profits or losses. The rate used to convert return into points is set before you enter. For example, $1,000 net profit on a $100,000 starting balance is a 1% return. This is game performance, not $1,000 you can withdraw. ## Added points These awards add to trading points: | Award | Points | | -------------- | ---------------------------------------------------------- | | Stage boost | Points earned every second while its objective is met | | Profit banking | 100 per new eligible profit milestone, up to 2,000 per run | | Mission Ace | 100 after 60 continuous qualifying seconds, once per stage | In a five-stage game, Mission Ace can award up to 500 points. Other medals celebrate events without adding points. See [Boosts and rewards](/docs/gameplay/boosts-and-rewards.md) for qualification rules. ## Read score updates Profit, losses, boosts, and point awards change your score. Rank changes and cosmetic medals report an event without adding another award. Trading fees are already included in net performance. A fee message does not deduct them twice. Watch your rank as well as your score. An improving score can still leave you below the next elimination line. --- # 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/score.md?ask=&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.