Documentation
Find solutions to common issues and errors that may occur during installation, configuration, or while using the script.
Cause: the folder was renamed. The resource checks its own name on boot.
Solution: rename the folder back to qs-banking and restart.
Cause: the resource started before your framework, inventory or targeting resource. Adapters resolve once, on startup.
Solution: fix the loading order in your server.cfg. Anything that starts after qs-banking cannot be detected.
Detection order:
Layer |
|---|
Order |
|---|
Framework |
|
Inventory |
|
Cause: the schema was not imported, or the wrong file was imported for your framework.
Solution: execute sql/esx.sql or sql/qb.sql — only the one matching your framework.
If a column is missing rather than a table, the resource tries to add it automatically. When that fails it prints the exact
ALTER TABLEstatement — run that instead of re-importing the whole schema.
Cause: the item is stackable, or your inventory does not support metadata.
Solution: the item must be named creditcard and be unique. A stackable card cannot carry its own card number, tier and PIN.
Cause: the tier id in Config.CardTiers has no matching theme in the interface.
Solution: use one of the existing tier ids, or add the matching theme before creating a new one.
Cause: cards are only issued at a counter, never at an ATM.
Solution: check the distance limit, and that the branch is allowed to create cards — or enable Config.CreateCardEverywhere.
Cause: a deposit hold with autoRelease = false, at a branch nobody runs.
Solution: this is deliberate behaviour, not a bug. A banker with the finance permission must clear or return the deposit from Manage → Finance. To avoid it entirely, set autoRelease = true, or holdHours = 0 to flag deposits for the audit trail without freezing them.
Cause: your own resource is reading the raw balance.
Solution: subtract the held amount before any affordability check:
local held = exports['qs-banking']:GetHeldAmount(identifier)Cause: the branch is unowned, or the doors are not in the game's door list.
Solution: an unowned branch is public — its doors can never be locked. For doors the game doesn't know about, add this to your server.cfg:
setr game_enableDynamicDoorCreation "true"Staff also need the doors rank permission; the owner always has keys.
Cause: the property integration is off, or qs-housing is not running.
Solution: both gates must pass — Config.RealEstate.enable must be on and qs-housing must be started. When either fails, those sections are never sent to the interface, by design.
The property desk additionally requires an owned branch holding the realestate licence.
qs-housing has no BankHandover export — update it so keys follow the deedCause: your qs-housing version is outdated and lacks the handover export.
Solution: update qs-housing. The resource falls back to writing the deed directly, so ownership moves — but stale key holders may survive. Don't rely on the fallback.
Cause: the branch is owned, so approval is manual, or its treasury is short.
Solution: an owned branch always waits for a banker and pays out of its treasury — the grant is refused if the balance can't cover it. Only state-owned branches with autoApprove grant instantly.
Cause: the treasury is a working float.
Solution: this is intentional. A branch can never be drained below the amount it was seeded with, and that float stays with the branch when it is sold — otherwise buying and reselling would mint money.
Cause: repeated failed charges hit the retry limit.
Solution: the order is paused, not deleted. The player resumes it from the interface once they have the funds.
Cause: your locale file is incomplete or outdated after an update.
Solution: missing keys fall back to English automatically, so this is a warning, not a failure. Copy the missing key from the English locale into your language file.