> For the complete documentation index, see [llms.txt](https://docs.songofrising.com/song-of-rising-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.songofrising.com/song-of-rising-white-paper/gameplay.md).

# Gameplay

Much of the gameplay in Song of Rising is centered around Heroes, the utility-based NFTs that can gather resources with Professions and will eventually be able to participate in combat quests and even PVP. You can visit the hero market to buy Heroes and you can learn more about what makes each Hero unique in the Heroes section of this guide.

If you don't have enough RUBY yet to purchase a Hero, that's ok, too! You can invest what you do have through the RUBY (DEX fee sharing) or in the Farms (liquidity pooling) to begin earning more RUBY. Of course, you'll need to visit the Marketplace to trade for RUBY in the first place.

The possibilities for gameplay and earning in Song of Rising are many and varied, so don't hesitate to explore this guide further to learn more about the options available to you!


---

# 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.songofrising.com/song-of-rising-white-paper/gameplay.md?ask=<question>&goal=<endgoal>
```

`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.
