> For the complete documentation index, see [llms.txt](https://whitepaper.paydirt.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.paydirt.game/paydirt/pillars.md).

# Pillars

## Game-first Approach

Our goal is to create a game players will want to keep coming back to play. In other words, we place fun at the top of our priority list.

## Blockchain-optional

All blockchain features are optional and a wallet is not required to play.

## Accessible

The game will gradually introduce gameplay features and blockchain concepts to players with guided tutorials.

## Friendly

The community should be a friendly and inviting place.

## Game-as-a-Service (GaaS)

Continual updates will improve the game over time.

## Historical Accuracy & Authenticity

Every major element of the game design should have a well-researched connection to history.

## Entertain & Educate

Players should learn something new while also having fun.

## Immersive, Living World

Players should feel like they are stepping into the past and the world should feel alive.

## Vibrant, Sustainable Economy

The economy should be free of major flaws, loop holes and vulnerabilities and operate sustainably over a long period of time.

## Play & Earn

Players should be able to earn tokens which reward their time spent playing the game.

## Shared Ownership

Players should maintain ownership of the value they produce within the game.

## Openness & Interoperability

Players should be able to port value into and out of the game to participate in the wider metaverse and blockchain ecosystem.


---

# 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.paydirt.game/paydirt/pillars.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.