> For the complete documentation index, see [llms.txt](https://seeddao.gitbook.io/seed-tutorial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seeddao.gitbook.io/seed-tutorial/seed-go-earning/slove-earning.md).

# SLOVE Earning

In the SEED Verse, players are equipped with **NFT SEED Mons** to earn tokens by engaging in activities. Players can earn both **SLOVE** and **SEED**, depending on their chosen strategy.

**SLOVE/ SEED earnings per Energy** depends on three key factors:

1. **Quality of SEED Mon** – Base SLOVE earnings vary by SEED Mon Quality. Refer to the SEED Mon Qualities section for details about each type.
2. **SEED Mon’s Proficiency Attribute** – Higher Proficiency boosts SLOVE earnings per minute. From Level 0 to Level 30, players can ALL earn SLOVE. 
3. **SEED Mon’s Seeding Attribute** – Higher Seeding increases SEED earnings per minute. 
4. **Class of SEED Mon** – Higher Class SEED Mon can hunt more tokens and rewards since their attribute points are higher.

Once Energy is depleted, token earning stops. Players can either continue their activities without earning tokens or exit their session by holding the Stop button.


---

# 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://seeddao.gitbook.io/seed-tutorial/seed-go-earning/slove-earning.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.