> For the complete documentation index, see [llms.txt](https://whitepaper.nergame.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.nergame.app/the-platform/scores.md).

# Scores

Every challenge has its score points that will be given to the players only to complete the challenge. Also, there is the possibility to earn extra scores depending on the amount of time used to complete it.

The extra scores are assigned automatically using the challenge duration in seconds, being proportional to the vote quantity given by the viewers. If the challenge duration is short, the scores are high. An example is shown of a challenge of 30 minutes and with a fixed score of 1000:

((1800 seconds in total - 900 seconds of streaming) / 1800) \* 1000 total scores = 500 extra scores.

The scores ranking by each player can be seen on each event, and also the detailed scores on every challenge.

Also exists a global ranking where anyone can see the general scores get by all the players promoting effort and competitiveness.

**Important: To consider a challenge completed, at least 50% of the votes should be positive.**


---

# 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://whitepaper.nergame.app/the-platform/scores.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.