> For the complete documentation index, see [llms.txt](https://riventide.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://riventide.gitbook.io/whitepaper/economy-and-competition/leaderboards.md). # Leaderboards DISCLAIMER: All content here in is subject to change as the meta evolves through development, testing, and community feedback. No part of the Whitepaper is to be copied Riventide features multiple leaderboard categories that track different aspects of player performance. Your position on these leaderboards directly affects your Wyrm Tribute rewards. Strategic Implications * **PvE-focused players** should optimize for Valor and Conquest during the farming phase * **PvP-focused players** should use PvE to prepare optimal gear, then push their Arena league ranking * **Social players** benefit from building a strong referral or scholarship network — their referrals' Valor performance directly boosts their Fame and Sponsor standings * **Guild leaders** should recruit active PvE farmers to maximize collective Valor output The leaderboard system rewards specialization but also incentivizes building community through referrals, scholarships, and guild play. --- # 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://riventide.gitbook.io/whitepaper/economy-and-competition/leaderboards.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.