
Mejores FiveM Scripts 2025: Selecciones probadas con Resmon real...
Los scripts gratuitos son útiles para comprobaciones rápidas. Para servidores de producción, compare los paquetes completos para servidores o los scripts de pago con mantenimiento, teniendo en cuenta el framework y el caso de uso.
You want low hitch times, clean UX, and scripts that survive updates. This list gives you battle‑tested picks with realistic Resmon budgets, safe asegurar order, conflicts to avoid, and quick install notes for ESX and QBCore.
How we measured
Baseline on OneSync Infinity, fresh build, oxmysql, ox_lib, 64–128 slots, 15–30 players for load tests,/resmon 1on client and server profiler for spikes. Your numbers vary with map, density, and tick priorities, but these budgets hold up across typical RP stacks.
Policía
https://fivemx.com/cd-dispatch
Pick: Envío de CD
What it does: Modern dispatch with units, blips, call routing, hotkeys, and exports. Improves police response flow without drowning clients in UI.
Install notes: Add locale, set framework bridge, wire keybinds, and tune call filters. Make sure blip limits and alert throttles fit your city size.
Seguro asegurar order:
# libs → framework → jobs → target → dispatch ensure ox_lib ensure ox_target # or qb-target ensure oxmysql ensure qb-core # or es_extended ensure [jobs] # e.g. police job package ensure cd_dispatch
Typical Resmon: Inactivo 0.01–0.03 ms • Load 0.08–0.16 ms
ESX/QBCore notes: Works fine on both once bridges and job names align.
Known conflicts: Other dispatches that register the same alerts, duplicate blip managers, aggressive anti‑cheat event filters.
Empleos
https://fivemx.com/advanced-repojob
Pick: RepoJob avanzado
What it does: Full repo gameplay loop with contracts, impounds, and payments.
Install notes: Seed SQL, set society accounts, check vehicle class lists, and test impound release logic.
Seguro asegurar order:
ensure ox_lib ensure oxmysql ensure qb-core # or es_extended ensure [vehicles] ensure advanced_repojob
Typical Resmon: Inactivo 0.01–0.02 ms • Load 0.12–0.25 ms
ESX/QBCore notes: Verify billing exports and target system adapters.
Known conflicts: Multiple impound systems, custom tow scripts that take over vehicle state.
Vehículos
Pick: 0r CarControl
What it does: Seatbelt, cruise, windows, doors, engine controls with a clean radial.
Install notes: Bind keys, disable overlapping features in other vehicle packs.
Seguro asegurar order:
ensure ox_lib ensure qb-core # or es_extended ensure 0r_carcontrol
Typical Resmon: Inactivo 0.00–0.02 ms • Load 0.04–0.09 ms
ESX/QBCore notes: Standalone friendly. Uses common exports.
Known conflicts: Other seatbelt or cruise control scripts, duplicated radial menus.
UI / HUD
Pick: WAIS eHUD
What it does: Lightweight HUD with status, minimap polish, and vehicle info.
Install notes: Decide which status systems you expose. Turn off duplicate UI in framework configs.
Seguro asegurar order:
ensure ox_lib ensure qb-core # or es_extended ensure wais_ehud
Typical Resmon: Inactivo 0.00–0.02 ms • Load 0.05–0.12 ms
ESX/QBCore notes: Ships with both bridges.
Known conflicts: Running more than one HUD, weapon wheel edits from other UI packs.
Inventario
Pick: Inventario LS V2
What it does: Modern inventory with grids, stacks, hotkeys, and shops.
Install notes: Migrate item names, verify weight rules, and convert stash IDs. Test robbery and drop rules.
Seguro asegurar order:
ensure ox_lib ensure oxmysql ensure qb-core # or es_extended ensure ls_inventory_v2
Typical Resmon: Inactivo 0.01–0.03 ms • Load 0.22–0.40 ms
ESX/QBCore notes: Confirm usable item events and metadata schema.
Known conflicts: Any second inventory, legacy shops, or old weight systems left enabled.
Housing
Pick: Vivienda S4
What it does: Ownable houses, keys, shells, furniture, and entry points.
Install notes: Bake IPLs if required, check doorlocks, and set shell streaming priorities.
Seguro asegurar order:
ensure ox_lib ensure oxmysql ensure qb-core # or es_extended ensure doorlock # your chosen lock system ensure s4_housing
Typical Resmon: Inactivo 0.00–0.02 ms • Load 0.12–0.28 ms
ESX/QBCore notes: Validate society billing and property taxes.
Known conflicts: Duplicate doorlock systems, furniture scripts that spawn objects on the same props.
Bancario
Pick: Banco Okok
What it does: Clean banking UI with accounts, statements, transfers, and ATM support.
Install notes: Point to oxmysql, clear duplicate ATM handlers, and log large transfers.
Seguro asegurar order:
ensure ox_lib ensure oxmysql ensure qb-core # or es_extended ensure okokBanking
Typical Resmon: Inactivo 0,00–0,01 ms • Load 0.05–0.12 ms
ESX/QBCore notes: Map job and society accounts during migration.
Known conflicts: Other banking UIs, ATM scripts, or fee calculators.
Teléfono
Pick: Teléfono LB
What it does: Feature phone that integrates with SaltyChat for realistic calls and radio.
Install notes: Install TeamSpeak + SaltyChat plugin first. Configure call audio, radio perms, and voice ranges. See our SaltyChat download y CrewPhone for SaltyChat pages.
Seguro asegurar order:
# Voice first, then phone ensure pma-voice # or SaltyChat bridge resource ensure lbphone
Typical Resmon: Inactivo 0.01–0.02 ms • Load 0.07–0.15 ms
ESX/QBCore notes: Check contact sources, job apps, and billing exports.
Known conflicts: Multiple phone frameworks, voice plugins loaded twice, radio channel managers.
Economía
Pick: Sistema Económico
What it does: Prices, taxes, payouts, dynamic multipliers, and money sinks.
Install notes: Lock currency decimals, cap multipliers, and stage changes on staging first. Log deltas.
Seguro asegurar order:
ensure ox_lib ensure oxmysql ensure qb-core # or es_extended ensure economy_system
Typical Resmon: Inactivo 0,00–0,01 ms • Load 0.08–0.20 ms
ESX/QBCore notes: Align accounts and bills to avoid dupes.
Known conflicts: Parallel tax scripts, double salary loops, donation perks that bypass sinks.
Utilities
Pick: Objetivo de CA
What it does: Eye target interactions for peds, props, and zones.
Install notes: Pick one target layer across the city. Do not run two. Prune legacy 3D text prompts.
Seguro asegurar order:
ensure ox_lib ensure qb-core # or es_extended ensure ac_target # or ox_target / qb-target
Typical Resmon: Inactivo 0,00–0,01 ms • Load 0.03–0.07 ms
ESX/QBCore notes: Replace old interaction calls with exports.
Known conflicts: Running ox_target and qb-target together, duplicate draw loops.
Side‑by‑side comparison
| Categoría | Elegir | Idle ms | Load ms | Framework | Difficulty |
|---|---|---|---|---|---|
| Policía | Envío de CD | 0.01–0.03 | 0.08–0.16 | ESX/QBCore | Medio |
| Empleos | RepoJob avanzado | 0.01–0.02 | 0.12–0.25 | ESX/QBCore | Medio |
| Vehículos | 0r CarControl | 0.00–0.02 | 0.04–0.09 | Standalone + ESX/QBCore | Fácil |
| UI/HUD | WAIS eHUD | 0.00–0.02 | 0.05–0.12 | ESX/QBCore | Medio |
| Inventario | Inventario LS V2 | 0.01–0.03 | 0.22–0.40 | ESX/QBCore | Hard |
| Housing | Vivienda S4 | 0.00–0.02 | 0.12–0.28 | ESX/QBCore | Medio |
| Bancario | Banco Okok | 0.00–0.01 | 0.05–0.12 | ESX/QBCore | Fácil |
| Teléfono | CrewPhone for SaltyChat | 0.01–0.02 | 0.07–0.15 | ESX/QBCore | Medio |
| Economía | Sistema Económico | 0.00–0.01 | 0.08–0.20 | ESX/QBCore | Medio |
| Utilities | Objetivo de CA | 0.00–0.01 | 0.03–0.07 | ESX/QBCore | Fácil |
How to test your server like a pro
- Update artifacts and start with a clean boot.
- Join alone and set
/resmon 1. Note idle ms for 60 seconds. - Spawn typical load: 10–20 players, 5–10 vehicles, one active job loop.
- Trigger the script’s peak actions. Example: several dispatch calls, repo seizures, inventory drag‑drops.
- Record load ms and mark spikes above +0.10 ms.
- Disable overlapping scripts one by one to isolate spikes.
- Move heavy resources to the bottom of
servidor.cfgto reduce startup contention. - Rinse and repeat after config tweaks.
- When done, hard restart and confirm idle budgets again.
- Read our guide on how to use Resmon y optimize performance.
Preguntas frecuentes
1) What is a good idle budget per resource?
Aim for ≤0.02 ms. Some UI or inventory modules sit around 0.03 ms. Above that, profile for loops.
2) How do I order asegurar safely?
Libraries → database → framework → centro jobs → interaction layer → feature scripts → UI. Never load two frameworks.
3) Why do my numbers differ from yours?
Maps, player density, tick priorities, and timers matter. Use the checklist above and compare idle vs action spikes, not only averages.
4) What conflicts kill performance fastest?
Duplicate HUDs, two target systems, two inventories, stacked doorlocks, and multiple dispatches. One of each category only.
5) How do I update without breaking?
Stage updates on a copy, diff configs, run the load test, then deploy. Keep a rolling changelog of config deltas.
6) ESX or QBCore: does the framework change budgets?
Tiny differences. The resource code and your config choices drive budgets more than the framework.
Next up: After installing your picks, follow our full guides on use Resmon y optimize performance to lock in stability.






