> For the complete documentation index, see [llms.txt](https://docs.ferrisgames.com/ferris-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ferrisgames.com/ferris-docs/plunder-engine/getting-started.md).

# Getting Started

## Sign Up For Ferris Games 

To create an account on the Ferris Games Developer Console, visit <https://console.ferrisgames.com/> and click the "Create Account" button in the top right corner of the screen.

## Get your Game ID

Once you have filled out this information, you can find your Game ID in the top left corner of the header. Your Game ID will be a unique identifier for your game on Ferris Games.

After signing up, you will be prompted to create a new project. Enter the following information about your game; example:

* Name: Psyker
* Platform: Windows
* Category: Arcade
* Game Type: Fighter
* Description: A fighting game set in a dark and gritty cyberpunk world.

Once you have provided this information, click "Create Project". You can now find your Game ID in the top left of the header.


---

# 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.ferrisgames.com/ferris-docs/plunder-engine/getting-started.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.