> 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/uk-carrier-strike-group-v2/supercarriers/miltech-universal-carrier-toolbar.md).

# Miltech Universal Carrier Toolbar

UK Carrier Strike Group V2 uses the Miltech Universal Carrier Toolbar - which you may be familiar with if you have used Supercarrier Pro before.

The in-sim Toolbar provides a common platform for all Miltech Carriers to be located in the World (providing Bearing and Distance to nearest carriers), as well as a platform to manage carriers' elevators, animations; teleport to Carrier, Hangar and Approach; and sync with Multiplayer.

The app will automatically switch to the UK Carriers UI when in near proximity to one of these ships.

## App Overview

UK Carriers UI Mode does not feature LRLS, FLOLS or LSO/Scoring, and as such it does not have a landing page.

[Controls Tab](/uk-carrier-strike-group-v2/supercarriers/miltech-universal-carrier-toolbar/controls-tab.md)

[Settings Tab](/uk-carrier-strike-group-v2/supercarriers/miltech-universal-carrier-toolbar/settings-tab.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/uk-carrier-strike-group-v2/supercarriers/miltech-universal-carrier-toolbar.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.