n1nja’s taximeter displays a distance-based fare to a driver and passengers. The manifest declares version 1.0.3 and no ESX or QBCore dependency. The reviewed code contains no bank deduction, passenger payment or persistent billing integration.
Fare, controls and history
The Lua client samples vehicle movement each second and multiplies accumulated distance by Config.FareRate. Distance is displayed in metres: the supplied rate of 0.5 therefore produces a displayed fare of $500 over 1,000 metres. Choose a rate for your server’s economy; there is no separate waiting-time charge in this calculation.
X toggles the display; it does not start or stop fare calculation. The other controls are configured in Config.Keys. The supplied vehicle list includes taxi, kuruma and adder, so replace it with your intended fleet. Config.PauseOnReset controls whether resetting pauses the meter.
Ride history is a client-side Lua table, capped at ten entries by default. Resetting a non-empty ride records its fare and distance. There is no database or persistent storage path, so do not describe this as a durable trip log across reconnects or resource restarts.
Server validation and test checklist
The normal client restricts meter control to the driver, but the server handlers do not verify that the sender drives the submitted vehicle. Passenger reporting accepts a client-provided recipient list, and meter updates relay client-provided fare and distance. Validate vehicle membership, sender permissions, data types and update frequency before public use; never use these values directly as authority for billing.
Place the resource in a taximeter folder and configure it before starting it on a development server. Test driver and passenger displays, start/pause/reset, vehicle changes, a measured route and reconnecting after a recorded ride. Confirm any separate payment system independently.
Source and review scope
Source checked on 10 September 2026 at revision 36d7b3931de28965ad0139c7018534382977f801. Findings are based on the manifest, configuration, Lua and browser UI source; no multiplayer synchronization or fare accuracy test was performed.