Adding the compass
Add BPC_Compass to your pawn and tune its settings.
BPC_Compass is the per-player brain of the system. It builds the compass HUD, handles the marking inputs and keeps every marker updated on screen. The HUD is created for you; you don't add any widget to the viewport yourself.

Requirements
The component must sit on a Pawn or Character, not on a PlayerController or PlayerState. The pawn needs a Camera Component, because marks are traced forward from the camera. The HUD is only shown to the player who controls that pawn.
BPC_Compass settings
Select the component in your character Blueprint to see these values in the Details panel.
| Setting | Default | What it does |
|---|---|---|
Mark Range |
10000000 | How far a player can mark, in centimeters. The default equals 100 km, which is effectively unlimited. |
Remove Mark Threshold |
200 | If a player marks again closer than this distance (cm) to their existing mark, the mark is removed instead of a new one being placed. Default is 2 m. |
Max Number Of Danger Markers |
3 | The most temporary marks (Danger and Item) one player can have at once. When the cap is reached, the oldest one is removed. |
Add Player Marker |
true | When on, a Player marker is attached to this pawn so teammates can see the player on their compass. |
Update Interval |
0.01 | How often (seconds) marker positions refresh on screen. Lower is smoother, higher is cheaper. |
Project Setting |
DA_ProjectSetting |
The data asset that defines every marker type's look and the player colors. Usually leave it; if you want different setups (say, per game mode), duplicate it and assign the copy here. |
Unknown Item Data |
Item · 15 s | The look of an Item ping placed on something without BPC_AutoMarker (key 3 or the menu's Item option). It uses the same marker settings. |
Single Click |
false | Not connected to the marking logic in this version, so changing it has no effect. Leave it at the default. |
Marker Spawn Data |
Internal value filled in when a mark is created. Don't edit it. |
Tip
For tactical games where far pings feel unfair, try a Mark Range of 30000 (300 m). With lots of markers, an Update Interval of 0.03 usually still looks smooth; 0.01 is roughly every frame.