> For the complete documentation index, see [llms.txt](https://docs.pixudi.com/pixudi-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixudi.com/pixudi-manual/francais/introduction/rangs.md). # Rangs Nos cartes de liste blanche n'étaient pas seulement destinées à être des cartes à accès anticipé, mais quelque chose de plus, quelque chose de plus magique... Et nous avons décidé d'organiser une telle promotion, chacun pourra obtenir son propre rang unique pendant toute la durée du jeu !

Nom du grade	Nombre de cartes de liste blanche	Image
Repham	10
Fapro	15
Vestagro	25
Loderis	50
Deluneris	75
Domentorum	125
Vadracum	165
Draposter	250
Sopevisor	350
Fidecrylan	500
Imcasidras	1000
Crunivero	156492	???

Plus tard, nous listerons les avantages pour chaque rang dans le tableau, mais il s'agit de bonus à grande échelle tels que : * Bonus mensuels * Accès anticipé aux nouveaux tableaux ! * Skin de personnage exclusif * Peau de dragon exclusive * Abonnez-vous à INGEMS * Certificat Pixudien * et bien plus encore...sera édité sur cette page --- # 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://docs.pixudi.com/pixudi-manual/francais/introduction/rangs.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.