Skip to content

Resolución de problemas

Troubleshooting

Nothing happens at a pump

Check Config.Interaction. On 'target' you need a target resource running — ox_target, qb-target or qtarget — and Config.Target set to 'auto' or the right name. If you do not run one, set Config.Interaction = 'textui' and pumps, chargers and the manage marker all fall back to an [E] prompt.

If the interaction appears but refuses, the pump prop is probably outside the station's radius. Turn Config.Debug on — it draws the zones.

A custom station MLO has pumps that do nothing

A pump is recognised by its model. Add the model to Config.PumpProps and make sure it stands inside a station's coords/radius.

The engine refuses to fuel

Config.Refuel.HoldEngineOff = true refuses to fuel a running engine. Turn the car off, or set it to false.

Using the jerry can does nothing

The item has to be registered as usable before the resource ever hears about it.

  • On ox_inventory, the entry needs client = { export = 'bupa-fuel.useJerryCan' }.
  • On QBox, QB-Core and ESX the resource registers the handler itself; the item only needs useable = true.
  • The item name must match Config.JerryCan.Item exactly, in lower case.

Do not swap in weapon_petrolcan — it is a weapon and will not work with any of this.

Two jerry cans merged into one

The item is stackable. Set stack = false on ox_inventory or unique = true on qb-style inventories. Each can carries its own fuel level, so stacking merges two different amounts into one slot.

Every car spawns nearly full / nearly empty

That is Config.Consumption.SpawnFuel. It is the range every unseen vehicle rolls in, and it is the biggest single influence on how often anyone visits a pump. Lower it to drive traffic to the stations, raise it to make fuel a background concern.

Fuel drains far too fast

Scale the whole Config.Consumption.Rpm table down — halving every value doubles how long everything lasts while keeping the differences between vehicles intact. If it is only certain vehicles, that is Config.Consumption.Rate for their class; industrial (3.0), helicopters (3.5) and planes (4.0) are deliberately heavy.

A vehicle never needs fuel

Its class has a tank of 0 in Config.Consumption.Tank. Cycles (13) and trains (21) ship that way on purpose. Give the class a tank size to make it burn fuel.

An electric car cannot be filled at a pump

Correct. Anything in Config.VehicleFuel.Electric only works at a charger. If a station has no charger field it cannot serve EVs at all — add one, or send them elsewhere.

A station's tanks are always full and it has no dashboard

It is a public station — purchasable = false. Public stations hold permanently full tanks, skip stock and deliveries, and cannot be owned. Check whether an admin flipped it from /fueladmin; that override is saved per station and wins over the config.

/fueladmin says I am not allowed

Grant the ace:

cfg
add_ace group.admin bupa.fuel allow

or add your licence identifier to Config.Admin.Developers, or add your admin group's name to Config.Admin.AdminGroups. Turn Config.Debug on and a denied check prints the player's name and id to the server console.

Customers pay but the owner gets nothing

Money only goes into a station bank if the station is owned. Sales at unowned and public stations disappear, which is intended.

Fuel level resets or desyncs between players

Fuel lives on the vehicle's fuel state bag. If another resource is also writing SetVehicleFuelLevel, the two will fight. Remove the other fuel script — running two at once will never work.

The station bank went negative or blank

It cannot. Values above Config.AntiCheat.MaxAmount are rejected and a corrupted balance is reset to zero on read. If a balance vanished, check the Bank page's log to see what left and when.

Item pictures are blank in the interface

They come from your inventory's image folder, detected automatically. On a renamed fork, point the resource at it:

lua
Config.UI.ImagePath = 'nui://my-inventory/web/images/'

Version check prints an error

The resource asks GitHub for the current version on start. An HTTP error there means your server could not reach raw.githubusercontent.com — a firewall or a temporary outage. It has no effect on anything the resource does; the check simply prints and moves on.