# Mission Logic Basics: Events, Actions, and Connections

Building a compelling mission is about more than just placing objects on a map. To create an engaging experience, you need to design a sequence of objectives, decide how the player progresses, and use connections between objects to control the mission flow. This guide will show you how to move beyond the basics and start shaping dynamic, interactive missions.

## Understanding Connections

### What are connections?

Connections are the links between the events and actions of your map objects. They define how the mission flows from one stage to the next, making your scenario interactive and responsive to the player.

* **Events** are signals an object sends when something specific happens (e.g., entering an area, timer expires, fire is extinguished).
* **Actions** are responses performed by objects when triggered (e.g., playing dialog, activating an objective, ending the mission).

### Why use connections?

Connections let you design missions that react to the player's actions, create branching or sequential tasks, and control when objectives or triggers become active.

### How to use connections

{% stepper %}
{% step %}

### Open the connections popup

Click on an object to open its detail editor. This will display actions on the left and events on the right:

<div align="left"><figure><img src="/files/Xj20LZI8UtKSeCD7FKZM" alt="" width="563"><figcaption></figcaption></figure></div>

You can also use the quick buttons that appear when you hover over the map object:

<div align="left"><figure><img src="/files/stM6VBYAxOnqnk6Cficb" alt="" width="375"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Create a connection

Hover over an event or action and click the add connection button:

<div align="left"><figure><img src="/files/jBAp5JoJJTOtBKgK23W1" alt="" width="243"><figcaption></figcaption></figure></div>

Hover over another object to see its available actions or events:

<div align="left"><figure><img src="/files/DsBJIjIwOBI2c9YHEWGr" alt="" width="563"><figcaption></figcaption></figure></div>

Select the one you want to connect to, then confirm with the checkmark button:

<div align="left"><figure><img src="/files/ywYCAvc4Vjz3EyT7nEiJ" alt="" width="180"><figcaption></figcaption></figure></div>

Arrows on the map will display the connection, always pointing from the event (sender) to the action (receiver):

<div align="left"><figure><img src="/files/3phJWErcy4EDgpoTsUuh" alt="" width="383"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### View and edit connections

Open the Detail Editor or click the quick hover button. Hover over an event or action to see its current connections:

<div align="left"><figure><img src="/files/DSAlvLPQaGtqScpTSvJ2" alt="" width="374"><figcaption></figcaption></figure></div>

You can delete connections from this view as well.
{% endstep %}
{% endstepper %}

### More details:

* **There is no limit** to the number of connections.
* **Any objects** with available events or actions can be connected.
* If you delete an object, its connections are also removed automatically.
* **Tip:** Give every object a meaningful name to make it clear which object is connected.

## Next steps

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

[Adding a route to your mission](/miltech-mission-hub/guides/adding-a-route-to-your-mission.md)


---

# Agent Instructions: 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:

```
GET https://docs.miltechsimulations.com/miltech-mission-hub/guides/mission-logic-basics-events-actions-and-connections.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.