Flux Map: player visibility for your FiveM staff

Requirements and access

Flux Map requires a Premium license, OneSync, and the appropriate in-game permission. Open or close it with /flux map. Your dashboard role and in-game permissions serve different purposes; access to a dashboard does not automatically grant map access.

The server checks permission and license access. Configure who can use the map and spectator tools before introducing them into your moderation routine.

Find a player and review the context

Search the player list and use dimension and risk filters to narrow an investigation. Select a player from the list or a map marker to inspect the available context.

Routing buckets represent separate server dimensions. The map helps staff understand that context and choose who to review; it does not replace logs or the team’s analysis.

Risk helps prioritize review

Risk indicators help your team prioritize attention. A score or position on the list is not a finding that a player cheated, and does not authorize an automatic punishment.

Compare the available records, the current gameplay situation, and your framework behavior before deciding on a response. Adjust configuration when ordinary actions produce unexpected signals.

Authorized spectator and other Premium tools

Authorized spectator access is checked on the server. The session manages the staff member’s position and routing bucket and restores them when it ends or can no longer continue.

Premium also includes player screenshots and death reports. Screenshots require the additional dependencies included in the package. Review the evidence and context together rather than relying on a single observation.

Introduce the tools into your staff routine

Validate the installed resource and staff permissions on a test server before relying on them during a live incident. Technical demonstrations or synthetic map points do not establish capacity for the same number of connected players.

• Define which staff members can open the map and spectate.
• Confirm OneSync, the current resource version, and the installed dependencies.
• Review player search and dimension filters with your team.
• Combine observations with logs and document the moderation decision.