Lag is the enemy of roleplay. Discover the coding standards and server-side optimizations we use to keep Omlette Mods scripts running at peak performance.
Understanding the Resource Monitor
In FiveM, performance is measured in milliseconds (ms) representing the time it takes the client or server to execute a script's code per frame. A poorly written script might take 1.00ms or more, drastically lowering the FPS of players. The holy grail of optimization is achieving 0.00ms when idle.
Avoiding While Loops Without Waits
The most common cause of high CPU usage is an unoptimized while true do loop. If a loop is checking for a condition (like distance to a marker) but the player is far away, the loop should include a Wait(1000) instead of running every frame (Wait(0)). Dynamic wait times are crucial for performance.
Optimizing Native Calls
Calling FiveM natives is expensive. Avoid calling natives repeatedly inside fast loops. Instead, cache the results in local variables. For example, instead of calling GetPlayerPed(-1) every frame, define local ped = PlayerPedId() outside the loop or update it less frequently.
The Omlette Mods Standard
At Omlette Mods, every single script is heavily scrutinized for performance. We employ advanced techniques like distance-based rendering, event-driven logic instead of loops, and localized variables to ensure our products maintain a strict 0.00ms footprint when idle, and barely register when active.