> For the complete documentation index, see [llms.txt](https://sagaofveil.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://sagaofveil.gitbook.io/whitepaper/gameplay/rpg-elements.md). # RPG elements Our inspiration is old-school step-by-step RPGs so of course we got something from them. We have more than 50 playable classes with own features. {% embed url="" %} Also each character have some customization: * Armor sets * Weapons * Spells * Food to heal (consumable) How to get all of this? There are two ways. First one is to just buy for [**$LITR**](/whitepaper/usdlitr.md) token in our store. Second one is to find them on chests hidden across the procedurally generated map. The more rare NFT you get the higher chances to find chests you get. It needs to attach value to the rarity of NFTs without turning the game into pay to win. Our focus is first of all on 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://sagaofveil.gitbook.io/whitepaper/gameplay/rpg-elements.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.