> For the complete documentation index, see [llms.txt](https://toms-whitepaper.gitbook.io/tomclicker-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://toms-whitepaper.gitbook.io/tomclicker-whitepaper/game-tom-clicker/ranking.md). # RANKING Your position in the rankings is directly influenced by the number of TOM Points you farm during the season (even if you spend them in the shop). Here’s how it impacts your gameplay and rewards: ### 🏆 The Essence of Competition: * **Earning Points:** Every action you take, from tapping for TOM Points to completing tasks, referring friends and automatic farming with the upgrades from the store, contributes to your total points. * **Spending Wisely:** Interestingly, spending points in the shop for upgrades doesn’t detract from your ranking. This design encourages strategic investment to enhance your earning capabilities without penalty. * **Climbing the Ranks:** The more points you farm, the higher your rank. It’s a simple yet compelling motivation to stay active and strategic in your gameplay. --- # 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://toms-whitepaper.gitbook.io/tomclicker-whitepaper/game-tom-clicker/ranking.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.