FiveMX evidence standard
How FiveMX measures script performance.
A listing receives a performance result only after the exact downloadable package is installed and measured in a documented FiveM environment. Archive contents, developer marketing and category labels are not converted into low-resmon claims.
Minimum evidence for a resmon result
- Bind the test to the sold package. Record the product ID, current download-configuration hash and SHA-256 fingerprint of each tested ZIP.
- Publish the environment. Record the FXServer artifact, operating system, CPU, memory, framework and version, database adapter, OneSync mode and required dependencies.
- Define one repeatable scenario. State the location, commands, player actions, enabled feature and other resources that remain active.
- Warm up before sampling. Complete at least five minutes of normal use before the measured period.
- Measure for at least ten minutes. Capture client resmon at regular intervals and publish the active p95 in milliseconds, not only the lowest screenshot.
- Keep the boundary explicit. Client resmon does not prove server/database efficiency or high-player-count stability.
Minimum evidence for a high-player-count result
- State the real connected-player count; simulated clients or replayed events must be labeled separately.
- Run the representative gameplay scenario for at least 30 measured minutes after warm-up.
- Record server CPU, memory, frame/hitch warnings, database latency and resource timing alongside client resmon.
- Publish disconnects, script errors and failed actions rather than reporting only successful samples.
- Do not generalize one product/version result to the catalog or to a different framework stack.
What appears on a verified product result?
The product page states the measured date, scenario, duration, connected-player count, server artifact, framework, active resmon p95 and measurement method. The result disappears automatically when the product download configuration changes and remains unpublished until the new package is tested.
Current published coverage: 0 product-specific runtime benchmark(s).
What FiveMX does not claim
A “0.00 ms” screenshot, an unverified developer statement, a static code scan or a successful server start is not a high-player-count benchmark. A result also does not guarantee identical performance on another server. Buyers should reproduce the scenario on staging with their own framework, database and resource stack.
See the practical FiveM resmon guide et staging maintenance process.