> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementlabs.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Markers do not appear

> Diagnose markers that exist in game but are missing from the map, or shown without their name and icon.

## Symptoms

The map opens as expected, but:

* markers another resource created are missing from it entirely; or
* they are drawn, but with a generic icon and no name in the legend; or
* some resources' markers appear and others' do not.

## Likely cause

**Missing markers.** The map sees markers by watching how they are created. A resource that creates
markers without the map's integration in place creates them where the map cannot see them. This is
what the integration shipped with the release is for: it installs the observing part of the map into
every one of your resources.

Markers created **before** the integration was installed stay invisible even after installing it, so
a resource that creates all its markers when it starts needs a restart afterwards.

**Markers without a name or icon.** These are markers the map can see, but which carry no map
information. The map shows the properties the marker itself has; the legend name, category, cone and
the rest come from the creating resource calling `SetBlipMeta`. Without that call there is nothing
to show, so the marker falls back to the configured defaults.

**Some resources but not others.** The integration reaches the resources that existed when it was
run. A resource added afterwards was never visited.

## Resolution

### 1. Install the integration

Run the script for your platform, from inside the map's resource directory:

```text theme={null}
resources\[element]\element_map\windows-install-hooks-element_map.bat
```

```bash theme={null}
cd resources/\[element\]/element_map
./linux-install-hooks-element_map.sh
```

What it changes, and its prerequisites, are in [Product integrations](/concepts/integrations). Back
up your `resources` directory first.

### 2. Restart the server

A full restart, so every resource is loaded with the integration in place and recreates its markers.

### 3. Confirm the integration reached the resource

Open the `fxmanifest.lua` of a resource whose markers are missing. Near the top there should be a
line pointing into the map:

```lua theme={null}
client_script '@element_map/integrations/external-blips/client/blips.lua'
```

If it is absent, the script did not visit that resource. The usual reasons are that the resource was
added after the script was run, or that it lives outside the `resources` directory the script found.
Run the script again.

### 4. For markers without a name or icon

That is the creating resource's part. It attaches map information to the marker it created:

```lua theme={null}
local handle = AddBlipForCoord(-1037.0, -2738.0, 20.0)
SetBlipSprite(handle, 90)

exports.element_map:SetBlipMeta(handle, {
  name = 'Airport',
  category = 3,
})
```

The full set of fields is in [Exports](/products/map/reference/exports). If the resource is not
yours, its author has to add the call. The map cannot invent a name for a marker that has none.

### 5. After updating the map

An update replaces the integration and the installer scripts, so run the installer again and restart.

## Verification

Open the map and confirm the previously missing markers are drawn, appear in the legend with the
expected name and icon, and can be clicked.

Check one marker from each resource that was affected, not only the first one: the integration is
installed per resource, so one resource can still be missing while the rest are correct.