# Gamers L.A.B. Structure

## Summary

The Gamers L.A.B. system is designed to mirror conventional backend architecture, making it accessible and familiar to traditional game developers. 

Core entities such as **Players**, **Match Sessions**, **Login Sessions**, **Record Events**, and **Application-Level Data** are modeled explicitly on-chain. Each contract is engineered to balance structure and flexibility—providing a modular base for interoperable applications, while still allowing developers to store game-specific or abstract data using extensible metadata fields.

Entities such as players, sessions, and records also support custom key-value metadata, allowing developers to attach arbitrary game-relevant information without needing to modify the base schema. 

Additional support for common data is provided out of the box. For example, matches can store results such as win, loss, draw, fail, or not set, and players can be designated as either *human* or *NPC*. 

This approach ensures compatibility across different game genres and use cases while retaining enough consistency to support indexing, analytics, and system-level features.

The Gamers L.A.B. structure is purpose-built for gaming, prioritizing long-term data utility, interoperability, and ease of use. It provides the necessary scaffolding to support scalable, on-chain game data while accommodating the variability found across game types and gameplay models.

## High-Level Structure

<figure><img src="/files/xs0h9JgXtZo3uwJaD6oJ" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.gamerslab.gg/developer-guide/gamers-l.a.b.-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.