Draggy by TheStoicBear displays vehicle speed, elapsed time and drag-run thresholds. The reviewed version 1.0.0 reads QBCore exports on both client and server, so the shipped resource is not standalone. Setting useItem to false bypasses the item check but does not remove that framework dependency.<\/p>\n
Place fxmanifest.lua, config.lua, client.lua, server.lua and ui\/index.html directly inside draggy. Start qb-core and your selected inventory first, then ensure draggy. Use \/draggy while in a vehicle to toggle the display. The command checks vehicle presence, not whether you occupy the driver seat.<\/p>\n
Defaults are Config.inventory = ox, Config.useItem = true and itemName = dragchip. The ox branch checks whether the item exists in the inventory item definitions, not whether the player owns it. The qb branch asks the server for GetItemByName. Correct the ox ownership check before treating the item setting as an access restriction.<\/p>\n
The client samples about every 100 milliseconds. Speed thresholds are 60, 100 and 120 MPH; distance thresholds are one-eighth, one-quarter, one-half and one mile. Distance is straight-line displacement from the start position, not accumulated road distance. Use a straight, level route and consistent vehicle conditions when comparing runs.<\/p>\n
Timing arms at a speed of at most 1 metre per second and starts above that threshold. It is therefore not an exact zero-speed launch measurement. Power and torque values are a one-time wheel-power snapshot multiplied by fixed constants, not calibrated horsepower or torque measurements. Do not present these values as real-world dyno results.<\/p>\n
The HTML attaches a click handler to close-btn, but no element with that ID is present. The final Lua update also omits speed and elapsedTime although JavaScript calls toFixed on them. These paths can produce browser errors. Correct the missing-element and partial-update handling before relying on a clean interface.<\/p>\n
Test opening, stopping, reopening, changing vehicles, missing items and the completed run state on a development server. Results live in client memory and console output; the inspected server file contains only the item callback, not a persistent shared leaderboard.<\/p>\n