> 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/classes-and-heroes.md).

# Classes & Heroes

The Classes & Heroes feature in LootLocker allows you to define diverse player Classes, specifying their default loadout and the assets they can equip. This system is split into two levels—Base Classes and Hero Classes—enabling flexible configurations to support a variety of gameplay designs.

### Base Class

Base Classes serve as the foundation, letting you define essential archetypes like Wizard, Barbarian, or Cleric. For each Base Class, you can set a name, define equipable item types (Contexts), establish default loadouts (assets equipped by default), and attach key/value attributes for additional customization.

### Hero Class

Hero Classes build on Base Classes, allowing you to create specialized versions with unique default loadouts and refined rules around equipable assets (Exceptions). This enables more complex setups, for example a Healer (Base Class) who can also wield a 2-Handed Weapon, expanding customization options for advanced player roles.

### Use Cases

* Player Classes
* Unique Heroes
* Player Profiles
* Item equipping system
* Default character equipment

### How-to

* [Configure a Base Class in Web Console](/game-systems/classes-and-heroes/how-to/base-classes.md)
* [Configure a Hero Class in Web Console](/game-systems/classes-and-heroes/how-to/hero-classes.md)
* [Use Base Classes In-Game](/game-systems/classes-and-heroes/how-to/implement-classes-in-game.md)
* [Use Hero Classes In-Game](/game-systems/classes-and-heroes/how-to/implement-heroes-in-game.md)


---

# 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/classes-and-heroes.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.