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

# The Game

Pirate Nation v1 Beta Gameplay Loop

<figure><img src="https://2357161415-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlQIfXhxF7IAZQQagaLyV%2Fuploads%2FRA78qPcTbPdvGfCnEj6X%2FPN_Home_Island.png?alt=media&amp;token=3cc5fae4-d09e-4ffe-94a0-676b117580dd" alt=""><figcaption></figcaption></figure>

**Intro**

Pirate Nation is a fully onchain pirate themed RPG playable on Proof of Play Apex. Our plan is to create a massive world, filled with all sorts of adventures that we’re excited to build in the open alongside our community.

**Beta Status**

The game is in the early stage of development and will continue to develop over time. It is our goal to develop the game with a high level of transparency, so players always know what the dev team is working on, how it is changing, and what the ultimate vision is.

**We Welcome Player Feedback**

We want to hear what the players think of the game and what the players want to see changed and added in the future. This feedback will heavily influence the systems and features the dev team will work on as we continue to build Pirate Nation, so be vocal in Discord and let us know your thoughts!


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.piratenation.game/learn/the-game.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
