> For the complete documentation index, see [llms.txt](https://whitepaper.gravityhub.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.gravityhub.xyz/technology/archivement-system.md).
# Archivement System
From the Gravity team, we understand the need for players to be recognized for their achievements and effort invested in hours of gameplay. We also know that for developers, achievements can be used to encourage and reward player interactions and goals within your game. They are often used to track the number of kills, distances traveled, chests opened, or other common actions in games. They can also be used to help players discover different ways to play the game.
That's why we have designed an easy-to-integrate achievement system for developers within the Gravity SDK.
The mechanism is simple and can be completed in a few described steps in the SDK documentation, but we can summarize it as follows:
Step 1: Define the game achievements.
Step 2: Encapsulate the achievement functionality.
Step 3: Integration into the game.
Step 4: Testing and troubleshooting.
Step 5: Have fun!
In summary, our goal is to provide players with a rewarding experience by recognizing their achievements while making it easy for developers to implement an achievement system in their games.
---
# 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://whitepaper.gravityhub.xyz/technology/archivement-system.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.