Troubleshooting

/substances says I am not allowed

The editor is gated behind an ACE. Either grant it:

add_ace group.admin bupa.substances allow

or add your licence identifier to Config.Creator.Developers. Setting Config.Creator.UseAce = false removes the ACE check but leaves the developer list in force.

Using the item does nothing

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

• On ox_inventory, the entry needs server = { export = 'bupa-addictioncreator.useSubstance' }. Without it, the inventory never tells the resource the item was used.
• On QBox, QB-Core and ESX the resource registers the handler itself through the core; the item only needs useable = true.
• Check the item name in the editor matches the item name in your inventory exactly, in lower case.

The item disappears but nothing happens

That is your inventory consuming it on use. Add consume = 0 to the ox_inventory entry. The resource removes the item itself, but only once it has confirmed the dose is allowed.

Nothing appears in the editor after saving

The substance saved but is not published to clients. Check the server console on start — it prints how many substances were loaded. If it prints zero, the SQL was not imported or Config.Tables.Substances points at a table that does not exist.

Effects are far too strong

Every value on the Effects tab is the peak, multiplied by the curve. A blur of 1.0 with a curve that sits at the top for most of its length is unplayable, and that is working as designed. Either lower the value or reshape the curve so it spends less time at the peak. Use Apply to me and find out before your players do.

Players are overdosing constantly

The load threshold is crossed by taking things quickly, not by taking a lot over an evening. If it fires too often, either lower the per-substance cost in the editor or raise Config.Overdose.Threshold. A substance with a cost of 20 allows five doses before the load has decayed at all — check that number against how fast your dealers can sell.

Nobody ever reaches withdrawal

Withdrawal is measured from the last dose, so a player with a steady supply never sees it. If it is not firing at all, check the first stage's after value — 120 minutes is two real hours, which on a server with short sessions may simply never be reached. Bring the first stage forward.

Withdrawal jumped straight to a crisis after a break

Config.Withdrawal.RunsOffline is on and the player was away longer than the cap. Lower Config.Withdrawal.OfflineCap, or set RunsOffline = false to freeze the clock at logout entirely.

A medic cannot examine anybody

Check the job name matches Config.Medical.Jobs exactly and the grade is at or above MinGrade, then check the distance — both the examination and the treatment are verified on the server and refuse at more than Config.Medical.Distance plus a small margin.

The chart is nearly empty

That is the Medical tab doing its job. Each substance decides what a doctor may see, and a substance with everything switched off deliberately gives a medic nothing but a category. Turn the toggles back on for the substances you want readable.

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:

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.