GM-AntiBump is a standalone client resource by Goncal0_. Its version 1.1 manifest loads config.lua and antibump.lua without a framework dependency. It compares wheel suspension compression with a baseline and adjusts a driven vehicle’s maximum speed when a bump coincides with increasing speed.
Vehicle classes, not fitted tire types
The reviewed implementation chooses its threshold with GetVehicleClass. Config.BumpThresholds has entries for classes 0 through 9 and a Default fallback of 1000. It does not inspect installed off-road tires. Changing wheel cosmetics therefore does not select a different threshold in this code.
The driver loop runs every 50 milliseconds. Compression baselines are captured when the tracked vehicle changes; they are not continuously recalibrated. Outside a detected bump, the script repeatedly sets the maximum speed to 999.0. That can conflict with another resource that controls maximum speed.
Test handling and cleanup behavior
Keep the extracted manifest, configuration and client file together in one resource folder, and start that exact folder from server.cfg on a development server. Compare the same route with and without the resource using cars from several configured classes and an unconfigured class.
Test curb impacts, ramps, downhill acceleration, vehicle switching and passenger seats. Check interaction with cruise control, speed limiters and custom handling. The code has no resource-stop cleanup handler that restores a previous speed cap, so include stopping the resource during an active limit in your test.
Source and review scope
Source checked on 10 September 2026 at revision 03d0fec111c3ba2803f3fd22108c3a177dc3352a. These findings describe static code behavior; no driving, anti-cheat effectiveness or performance test was performed.