> For the complete documentation index, see [llms.txt](https://docs.fansports.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fansports.fun/getting-started/tournaments/tournament-scoring-basics.md). # Tournament Scoring - Basics ### Design Philosophy The **Fansports.fun** scoring system is built to reflect how **fans naturally judge player performances**. When watching a match, supporters instinctively know which actions deserve applause and which mistakes cause frustration. Our system is designed to capture that same intuition. Players are scored based on the **expectations of their position** (GK, DEF, MID, FWD), not just raw statistics. A good performance looks different for each role on the pitch. We will continue refining the system, but our core goal remains the same:\ **scores should feel natural, intuitive, and aligned with how most fans perceive the game**. Performance is subjective, and opinions will vary - but we aim to stay as close as possible to the consensus view. ### Position Examples **Goalkeepers**\ Rewarded for clean sheets, saves, commanding their area, and good distribution. Mistakes significantly reduce scores, even in a clean sheet win. **Defenders**\ Clean sheets matter, but defenders who tackle, intercept, and contribute in build-up play score higher than those with a quiet game. **Midfielders**\ Expected to influence the match overall. Goals and assists boost scores, but all-round involvement is key. **Forwards**\ Goals are important, but efficiency matters. Clinical finishers and forwards who contribute to overall play score higher than those who miss big chances. --- # 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.fansports.fun/getting-started/tournaments/tournament-scoring-basics.md?ask=&goal= ``` `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.