> For the complete documentation index, see [llms.txt](https://docs.miltechsimulations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miltechsimulations.com/miltech-mission-hub/detailed-documentation/map-objects/uk-carrier.md).

# UK Carrier

If you have the [Broken mention](broken://spaces/LeWXMh3aXYekAwqEAPs6) addon, you can place the carriers in the world. You can also use the carrier as spawn point.

{% hint style="warning" %}
You can only have **one** carrier in a mission. This includes carriers that are already placed in the world. If you have multiple carriers, they will interfere.
{% endhint %}

### Attributes

<table data-header-hidden data-full-width="false"><thead><tr><th width="109.99993896484375">Attribute</th><th>Description</th></tr></thead><tbody><tr><td><strong>UK Carrier Type</strong></td><td><p>Carrier to spawn. Can be:</p><ul><li>HMS Prince of Wales Moving</li><li>HMS Prince of Wales Static</li><li>HMS Queen Elizabeth Moving</li><li>HMS Queen Elizabeth Static</li></ul></td></tr><tr><td><strong>Orientation</strong></td><td>Heading of the carrier in true degrees north (not equal to magnetic north)</td></tr><tr><td><strong>Spawn on Carrier</strong></td><td>You can use the carrier as spawn point. You can only set 1 spawn point in a mission.<br>The aircraft will spawn 'Ready to go'.</td></tr></tbody></table>

### Actions

**UK Carrier** doesn't have any actions.

### Events

**UK Carrier** doesn't have any events.

## See also

UK Carrier Strike Group documentation: [Broken mention](broken://spaces/LeWXMh3aXYekAwqEAPs6)

[Supercarrier](/miltech-mission-hub/detailed-documentation/map-objects/supercarrier.md)

[Ship](/miltech-mission-hub/detailed-documentation/map-objects/ship.md)

[Spawn](/miltech-mission-hub/detailed-documentation/map-objects/spawn.md)


---

# 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.miltechsimulations.com/miltech-mission-hub/detailed-documentation/map-objects/uk-carrier.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.