Player Marker Device visual effects still cannot be disabled (2+ years, still unfixed)

Summary

Player Marker and Beam randomly appear on players even when not granted and Beam is set to Hidden

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

1- Place a Player Marker device in a Creative / UEFN island.
2- Set Beam to Hidden.
3- Set On Game Start Give Player the Marker to None.
4- Do not grant the marker to any player through devices or Verse logic.
5- Start the game and let players join the map.
6- Observe certain players spawning with a Player Marker already attached.
7- Attempt to Detach the marker from the affected player.
8- Grant the Player Marker manually to the same player, then attempt to Detach again.

Expected Result

No Player Marker should be attached to players unless explicitly granted.
Detach should fully remove the marker from the player.
Marker state should be fully controllable and reversible.

Observed Result

Some players receive a Player Marker immediately upon joining the map, even though it was never granted.
This marker behaves like an unremovable base layer:
Calling Detach has no effect on it.
The marker cannot be removed or hidden.
If the player is granted a Player Marker manually:
A second “layer” is applied.
Detach only removes the manually granted marker.
The original marker remains permanently attached.
This results in multiple marker layers, where only user-applied layers are controllable.

Platform(s)

All the platforms

Island Code

9862-4661-6699

Upload an image

Additional Notes

Gameplay Impact:

This breaks gameplay systems that rely on controlled marker assignment.

Example:
Markers used to indicate Top 1 / Top 2 / Top 3 players.
Due to this bug, random players may appear as Top players simply by joining the map.

This causes:
Incorrect visual information.
Player confusion.
Loss of trust in ranking and reward systems.

The issue is inconsistent and player-specific:
It may occur for some players and not others.
It may occur on first join and not on later joins, or vice versa.
The marker behaves as if it is applied internally by the engine.
This issue has existed for over two years and remains unresolved.

FORT-1049489 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.