TCZ-Speedtraps for FiveM

TCZ-Speedtraps adds configured speed-detection zones to a QBCore server. Version 1.0.0 declares qb-core and ox_lib dependencies. Its server code can add or remove bank money; this is an economy integration, not just a visual radar.

Validate detections before enabling money changes

The server accepts the trap name and speed from the client. It checks that the named trap is enabled and applies a server-side cooldown, but does not validate the speed’s type, the player’s proximity to the trap or whether the player is driving. Plate filtering does not establish that a genuine detection occurred. Correct these checks before connecting the resource to a live economy.

Thresholds are minimum speeds, evaluated in their configured order. With the supplied hospital example, speeds below 35 mph match nothing, 35 through below 70 select a $100 bank reward, and 70 or above select a $200 deduction. Keep thresholds ordered from low to high; the last matching entry wins. This does not reward every driver who stays below a speed limit.

Configuration and testing

Start qb-core and ox_lib before tcz-speedtraps. Review Config.Global.MetricSystem, each zone’s coordinates and radius, thresholds, amounts, cooldown and RestrictedPlates. The plate filter matches text patterns within a plate; it is not a verified emergency-job permission check.

Detection runs when a client enters the zone, rather than continuously while it remains inside. Test both threshold boundaries, leaving and re-entering, passenger seats, restricted plates, insufficient bank funds and cooldown expiry. Confirm that rejected detections never alter balances.

Source and review scope

Source checked on 10 September 2026 at revision afdcc5bd03c231757f60f5ce67cdf99e1c1bde99. This is a static review of the manifest, configuration and client/server code, not a successful multiplayer or economy test.

Review the TCZ-Speedtraps source