1. Confirm integration with your framework
Record your framework, version and main customizations. Flux includes integration for vRP/vRPex and adapters for ESX, QBox and Creative variants. This does not certify every version or resource combination. For QBCore or a custom framework, confirm your exact setup with support before purchasing.
The review should cover player identification, permissions and integration with the ban system. A tool can open correctly while those areas still need attention. Use the compatibility guide to prepare the discussion with your technical team.
2. Separate dashboard management from in-game access
Check who can manage the license, change settings and only read information. Flux distinguishes owner, technician and observer roles in the dashboard. Those roles are independent of permissions inside the server: inviting someone to the dashboard does not automatically grant in-game tools.
If you need Flux Map, confirm Premium, OneSync and the appropriate permission. In a test environment, your team should check both an authorized account and an account without access. The requirements and setup guide helps plan that work; installation instructions remain in customer documentation.
3. Assess what helps staff investigate
Ask how staff find records, relate an alert to its context and record the reason for a decision. Flux provides dashboard records and observation tools. Premium includes screenshots, spectator mode and death reports; screenshots depend on additional resources and session conditions, so not every record will contain one.
Flux Map helps locate players and prioritize review by routing bucket and risk. A score is not proof of cheating and does not authorize automatic punishment. Staff need to compare records and gameplay context with the community's moderation policy.
4. Plan changes and validation
Agree on a maintenance window, a person responsible for the setup and a way to check affected workflows in a test environment. Keep a current backup and plan a full server restart. Review Flux updates for relevant changes; a release note does not establish that your server has received them.
Measure resource usage in your own environment. Hardware, players, scripts and enabled rules affect the result. A demonstration using synthetic map points does not measure the load of real connections and must not be used to promise server capacity.
5. Check the offer and purchase conditions
New Flux purchases are available on Premium. References to Standard in historical records or existing-customer documentation do not represent a new offer of that plan or remove those customers' rights. Review plans and pricing, check duration, currency and total at checkout, and read the purchase and refund conditions before confirming. The current public guide identifies the Terms of Service as Portuguese; clarify questions with the team before purchasing.
Give support your framework version, customizations, required tools and operational questions. The choice becomes clearer when each requirement has a documented answer and someone responsible for validating it.
Confirm the setup before purchasing
Support is provided in Portuguese and English through Discord tickets. Confirm your framework, dependencies, and any language needs with the team. The Terms of Service are currently available in Portuguese; review them before purchasing: Terms of Service.
Contact support ↗