> 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/objective.md).

# Objective

Objectives are messages that show on the HUD. They tell the player what to do. But they're also a way to structure your mission (see [Building Detailed Missions: Objectives, Triggers, and Activities](/miltech-mission-hub/guides/building-detailed-missions-objectives-triggers-and-activities.md)).

### 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>Active On Start</strong></td><td><strong>Enabled:</strong> the objective will show when the mission starts.<br><strong>Disabled:</strong> you need to activate this objective during the misssion.</td></tr><tr><td><strong>Objective Title</strong></td><td>Text that is displayed to the player on the mission HUD</td></tr><tr><td><strong>Objective Icon</strong></td><td>You can choose different icons for the message on the mission HUD</td></tr><tr><td><strong>Show Direction</strong></td><td>Show the player the direction to this objective (where it's placed on the map)</td></tr></tbody></table>

### Actions

<table data-header-hidden><thead><tr><th width="110">Action</th><th>Description</th></tr></thead><tbody><tr><td><strong>Activate</strong></td><td>The objective will show on the HUD. Also fires the <em>Activated</em> event.</td></tr><tr><td><strong>Successful</strong></td><td>Will turn green on the HUD and disappear. Also fires the <em>Successful</em> event.</td></tr><tr><td><strong>Failed</strong></td><td>Will turn red on the HUD and disappear. Also fires the <em>Failed</em> event.</td></tr><tr><td><strong>Aborted</strong></td><td>Will disappear from the HUD. Also fires the <em>Aborted</em> event.</td></tr></tbody></table>

### Events

<table data-header-hidden><thead><tr><th width="109.99993896484375">Event</th><th>Description</th></tr></thead><tbody><tr><td><strong>Activated</strong></td><td>Fired when the objective is activated. <em>Example usage: turn on a trigger that will later complete this objective.</em></td></tr><tr><td><strong>Successful</strong></td><td>Fired when the objective's <em>Successful</em> action is executed. <em>Example usage: turn on the next objective.</em></td></tr><tr><td><strong>Failed</strong></td><td>Fired when the objective's <em>Failed</em> action is executed. <em>Example usage: fail the mission.</em></td></tr><tr><td><strong>Aborted</strong></td><td>Fired when the objective's <em>Aborted</em> action is executed. <em>Example usage: turn on an alternative objective.</em></td></tr></tbody></table>

## See also

[Building Detailed Missions: Objectives, Triggers, and Activities](/miltech-mission-hub/guides/building-detailed-missions-objectives-triggers-and-activities.md)

[End Mission](/miltech-mission-hub/detailed-documentation/map-objects/end-mission.md)

[Marker](/miltech-mission-hub/detailed-documentation/map-objects/marker.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/objective.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.
