> For the complete documentation index, see [llms.txt](https://docs.lootlocker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lootlocker.com/game-systems/overview.md). # Overview Game Systems are the core features in LootLocker that drive your game’s progression and player engagement. From meta-systems that keep players coming back, to classification and reward mechanics, to feedback channels for player-created content, Game Systems provide the foundational tools to enhance player retention and interaction. The following Game Systems features are available in LootLocker: * [Classes & Heroes](/game-systems/classes-and-heroes.md): Define and manage base and hero classes, each with unique loadouts and asset equip exceptions. * [Feedback](/game-systems/feedback.md): Enable players to provide feedback on each other, user-generated content, or the game itself. * [Leaderboards](/game-systems/leaderboards.md): Track player or generic rankings, with options for time-based resets and rewards. * [Progressions](/game-systems/progressions.md): Set up point-based progression systems with customizable tiers and rewards. * [Triggers](/game-systems/triggers.md): Grant rewards dynamically based on player actions. --- # 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.lootlocker.com/game-systems/overview.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.