> For the complete documentation index, see [llms.txt](https://legendsdoc.lovely.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legendsdoc.lovely.finance/glossary.md).

# Glossary

**Definitions of key terms and concepts used in the game.**

1. **Lovely Coins**: In-game currency earned through gameplay (tapping the screen). These can be converted into tokens.
2. **Tokens**: Virtual assets derived from converting Lovely Coins. Tokens may have real-world value or be used for in-game purposes.
3. **Virtual Cryptocurrency Exchange**: The in-game system where Lovely Coins are managed and used, simulating a cryptocurrency trading environment.
4. **Tap to Earn**: The core gameplay mechanic involving continuous screen taps to accumulate Lovely Coins.
5. **Upgrade**: Enhancements made to the player’s virtual exchange, which improve its efficiency or earning potential.
6. **Admins**: The game administrators set the conversion rates between Lovely Coins and Tokens and oversee game operations.
7. **Gameplay**: The interactive experience of earning coins and upgrading the virtual exchange, designed to be engaging and rewarding.\ <br>


---

# 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://legendsdoc.lovely.finance/glossary.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.