# UI Nav Markers Must Be Enabled Each Round

<figure><img src="/files/kFsqDSFNa3XnlNitRwNU" alt="Cover image"><figcaption></figcaption></figure>

Navigation markers implemented in Forge may appear to stop functioning once a round concludes. This behavior is expected and can be addressed by refreshing the marker status for each new round.

<figure><img src="/files/KAjKORq6QM3CwAoMphWJ" alt="UI Nav Marker example"><figcaption><p>A UI Nav Marker displays a name, icon and its distance to the player.</p></figcaption></figure>

## Marker Persistence

When designing navigation systems, developers can build a list of UI Nav Markers at the start of the game. This list is not cleared when a round ends, meaning the same marker references remain valid and can be accessed in subsequent rounds.

## Refreshing Markers

Because markers do not automatically reactivate when a new round begins, the [Set Nav Marker Enabled](/scripting/nodes/ui-nav-markers/set-nav-marker-enabled.md) node must be used to make them visible again.

### Implementation Workflow

To maintain functional markers throughout a match, the following workflow is recommended:

* **Game Start**: Create and store a list of all necessary UI Nav Markers.
* **Round Start**: Iterate through the stored list and pass each marker into the `Set Nav Marker Enabled` node.

<figure><img src="/files/3Hi8wp79hMBDdb5VN0sb" alt="Set Nav Marker Enabled node"><figcaption><p>The Set Nav Marker Enabled node is used to toggle the visibility of a marker.</p></figcaption></figure>

{% hint style="info" %}
Since the list of UI Nav Markers persists across rounds, you do not need to rebuild the list at the start of every round, but they must be re-enabled every round.
{% endhint %}

***

## Source Data

* Discord thread: [UI Nav Markers need to be Enabled each round](https://discord.com/channels/220766496635224065/1422050068667826237/1422050068667826237)

#### <mark style="color:green;">Contributors</mark>

Okom


---

# 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://wiki.thescriptersguild.com/knowledge/scripting/guides-and-info/ui-nav-markers-must-be-enabled-each-round.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.