Map & monitoring
Both views use the full dashboard workspace, with a searchable player list on the right. Live information requires the resource to be connected.
World map
The 3D map itself remains available while the FiveM server is offline. Player markers appear only with live player data.
Search the list by player name, server ID or identifier. Select a player to inspect their position. Ped and vehicle markers reflect the telemetry reported by the resource; they are not a full remote rendering of the game world.
Use the map's coordinate control to copy a location. Camera controls keep the view above the map. Initial loading shows progress; after the map assets have loaded, moving around should not redownload them.
LiveWatch
Select up to 16 online players to open their game views, or use Select everyone to select the first 16 online players at once. Larger selections use a four-column grid on desktop. Remove a selection when you no longer need its stream, or use Clear to stop all selected views. This dashboard change works with existing resources and does not require a FiveM restart.
Capture depends on the player's game/NUI, browser support and connection quality. The display can use a 1920×1080 frame, but the actual frame rate and delay vary with the capture and transport conditions. More simultaneous streams use more client, server and browser resources.
Staff monitoring requires the corresponding team permission. Inform players and staff how your server uses monitoring and evidence, and restrict access to people who need it.
The dashboard retries failed or expired WebRTC sessions automatically. JPEG relay frames remain available while a stream connects. Leaving monitoring or hiding the tab stops its streams; returning reconnects selected players. Restrictive networks may need a configured TURN relay for direct video; STUN alone cannot connect every network. No game stream is guaranteed to reach 30 FPS on every client.
Resource 1.8.36 adds demand-based player snapshots, bounded frame batches and a non-blocking video render loop. These resource changes take effect only after the new protected resource is installed; website changes do not replace Lua files.
Offline or stale data
If the server disconnects, live players and streams are not historical replays. Recheck the resource connection rather than treating a frozen frame as a player's current screen. Saved bans, lookup and configuration remain separate from these live views.
