Skip to content
Vice Drip
FiveM answers

How do I check a FiveM script's resmon?

To check a FiveM script's resmon, join your server, open the F8 console, type `resmon 1`, and find the resource by name in the table that appears. Read its millisecond value twice: once while nobody is using the feature (idle) and once while actively using it (active). Record the FXServer artifact version, framework, and date alongside both numbers. A well-built resource idles at 0.00–0.02ms and stays under roughly 0.10ms in use.

In one lineChecking resmon means reading a resource's per-frame millisecond cost from FiveM's built-in monitor under stated conditions, so the number can be compared and reproduced.

The longer answer.

resmon is a client-side view of what each resource costs the game each frame, so it must be read from inside a running client on the server you are testing — a server console cannot show it. The default sort is alphabetical; clicking the column header or watching for the resource you care about is enough for a single script. The value you want is the CPU time column in milliseconds, and it will fluctuate; watch it for thirty seconds rather than reading one frame.

Idle and active are different measurements and both matter. Idle is the resource's cost when its feature is not in use: stand still, close any menus, and read the number. Active is the cost while you exercise it — open the menu, run the job loop, trigger the interaction. A resource with a high idle cost is running per-frame work for nothing; a resource whose active cost never returns to idle after you stop is leaking a loop. Both are defects regardless of what the feature does.

The number is only meaningful with its conditions. Two people can read different resmon values for the same script because artifact version, framework, other running resources, player count, and hardware all change it. That is why a seller's claim should come with method and date, and why your own measurement should be recorded the same way: script version, artifact, framework, what else was running, and what you were doing. Measure on staging with a resource list that matches production; a bare server flatters everything.

The checklist.

  1. 01Join the server as a client and open the F8 console.
  2. 02Type `resmon 1` and locate the resource by its folder name.
  3. 03Read idle: nothing open, standing still, watch for ~30 seconds and note the steady value.
  4. 04Read active: use the feature the way a player would and note the peak and the steady value.
  5. 05Stop using the feature and confirm the value returns to idle within a few seconds.
  6. 06Write down artifact version, framework, resource list, date, and what you did — a number without those is not a measurement.
  7. 07Compare against the budgets: idle 0.00–0.02ms, active under ~0.10ms sustained.
Go deeper

Where this is covered in full.

Related questions

People asking this also ask.

Next

Where to go from here.

Published 2026-09-06 · Last reviewed 2026-09-06 · Vice Drip · All answers