> For the complete documentation index, see [llms.txt](https://docs.trickys.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trickys.gg/games/carrier-command-2/game-guide.md).
# Game Guide
Carrier Command 2 is part flight sim, part real-time strategy. You take the role of crew on a highly automated small "Aircraft Carrier/Assault ship" on an ocean world far from earth.
The planet Telos has vast oceans with sporadic small island groups that have been chosen for mining and manufacturing. Politics, war, economics, terrorism and corruption have all lead to these small but lucrative islands on a distant planet being fought over. It is your job to secure these islands from our enemies and competitors.
The aim of the game is to eliminate the enemy carrier forces before they eliminate you, sometimes these are AI controlled, sometimes they are other human factions. Do not underestimate the task at hand.
All crew have access to every ship system and role from the carrier bridge. Many roles need to be filled to succeed: logistics, strategy, command, navigation, ground force control, air combat, recon, repair. All of these can be done by one person, or by a crew working together.
---
# 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.trickys.gg/games/carrier-command-2/game-guide.md?ask=&goal=
```
`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.