> For the complete documentation index, see [llms.txt](https://docs.milliononmars.com/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.milliononmars.com/whitepaper/glitter-tokenomics/player-creator-rewards.md).
# Player Creator Rewards
200M Glitter Tokens (20%) are dedicated to rewarding our players who create in the Million on Mars Metaverse.
This 20% was previously ear marked for Staking Rewards, but we have always been cautious about the Staking side of Tokenomics, and have decided to firmly press forward with our Structured UGC disruption of game development.
\
These player creations are mostly coming from our players using the Game Design Editor (GDE) and creating new Missions, Leaderboards, Hex Mini Games or new Crafting Chains.\
\
Additionally players will be rewarded for creating new images via our partnership with Scenario as well as creative efforts.\
\
This page will be getting much more clear and detailed updates on how and what it takes to get Glitter Rewards from creating and developing the Million on Mars Metaverse!\
---
# 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.milliononmars.com/whitepaper/glitter-tokenomics/player-creator-rewards.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.