Summary

I'd like to request exposing GET_VEHICLE_FUEL_LEVEL as a server-side native, implemented in the same way as the existing RPC-backed vehicle health natives (e.g. GET_VEHICLE_ENGINE_HEALTH).

Currently, vehicle fuel level can only be read on the client. Having this available on the server (through an RPC to the entity owner) would align it with other vehicle state getters that are already available in server scripts.

Motivation / Use cases

Being able to read vehicle fuel level on the server side would help with several common use cases:

• Persistent vehicle systems that want to save/restore fuel level accurately.
• Economy systems (e.g. billing players for fuel usage, logging fuel consumption).
• Server-side logging/analytics of vehicle usage.
• Anti-cheat or validation logic that needs to reason about vehicle state without relying solely on custom client->server sync.

Right now, the usual workaround is to mirror fuel state manually from client to server (e.g. via events or state bags), which adds boilerplate and room for desync.

Proposed behaviour

• Expose GET_VEHICLE_FUEL_LEVEL as a CFX server native.
• Implementation could follow the same pattern already used for other vehicle-related server natives:
  • Server native resolves the vehicle entity.
  • RPC is sent to the entity owner to invoke the client-side native GET_VEHICLE_FUEL_LEVEL.
  • The float result is returned back to the server script.

From the script author's point of view, once a valid vehicle entity exists on the server, it would look like this:

-- server example: assuming 'netId' is a valid network ID for a vehicle

RegisterNetEvent('myresource:checkFuel', function(netId)
    local src = source
    local veh = NetworkGetEntityFromNetworkId(netId)

    if veh ~= 0 then
        local fuel = GetVehicleFuelLevel(veh)
        print(('[fuel] vehicle %d has %.2f fuel (from %s)'):format(veh, fuel, src))
    end
end)