Alamo Studio Logo
Deployment

Troubleshooting

Common problems and how to fix them.

Shops / blips don't appear

  • Lua syntax error in config.lua. A missing comma or bracket stops the file loading. Check the server console for an error mentioning alamo-market or config.lua.
  • Resource not started. Confirm ensure alamo-market is in server.cfg.
  • Blip disabled. Check the location's blip.enabled isn't false.

"You are not allowed to use this shop"

The shop has job restrictions and the player doesn't qualify.

  • Verify the jobs names exactly match your framework's job names.
  • Check minJobGrade / per-job minGrade against the player's grade.

Player paid but received no item

The item name in the catalog must exist as a real inventory item. If it doesn't, the framework's AddItem silently fails while money is still removed.
  • Confirm the item name exists in your items list (ox_inventory, qb-core/shared/items.lua, ESX items DB, etc.).
  • Match the exact spelling/case used by your inventory.

Wrong language showing

  • Check Config.Locale is set to a file that exists in locales/.
  • If you added a custom locale, ensure the filename matches (e.g. frlocales/fr.json).
  • A missing file falls back to en and logs a warning in the console.

Theme / colors didn't change

  • Make sure only one :root block is active (uncommented) in variables.css.
  • --accent and --accent-rgb must be the same color.
  • Restart the resource or re-open the UI after editing.

"Too far from shop" on purchase

The server caps purchase distance at ~10m. The player must be standing in/near the marker when checking out. This is anti-cheat protection and is expected behavior.

Notifications don't show

  • With system = 'event', the notification resource that listens for your configured event must be running.
  • With system = 'custom', ensure Custom is a valid function (otherwise it falls back to framework).
  • Enable Config.Debug = true to see notify diagnostics in the console.

Still stuck?

Turn on debug logging and re-check the console:

config.lua
Config.Debug = true

Then restart and reproduce the issue — extra diagnostics will be printed.

Copyright © 2026