Skip to main content

​
The UI doesn’t load / panel is blank

The built UI is missing. fxmanifest.lua ships web/build/index.html, so the web/build/ folder must exist.
  • Confirm web/build/index.html and web/build/assets/ are present in the resource.
  • If you edited anything under web/, rebuild it: 
    cd web
bun install
bun run build
See Installation.

​
Players can’t interact with poles

Almost always a target mismatch. Config.Target must match a targeting resource you actually run.
  • Set Config.Target to 'ox', 'qb', or 'lib' to match ox_target, qb-target, or ox_lib zones.
  • ensure that target resource before nex_polecreator in your server.cfg.
  • Check InteractDistance isn’t too small for the player to reach the zone.
If Config.Target names a resource you don’t run, no interaction zones are created and nothing happens when players walk up to a pole.

​
Admin can’t open /poles

Access is gated by the ace permission and your framework admin groups.
  • Make sure the admin has the AdminPermission ace (default group.admin) via add_ace / add_principal.
  • If your admins are admins through the framework instead, add their group / permission to AdminGroups (default admin, superadmin, god).
  • Remember the check is also enforced server-side on every write, so granting it client-side only won’t help — set the real ace or group.
See Configuration.

​
Poles aren’t spawning

  • Confirm oxmysql is running and the nex_poles table exists (it is auto-created on start; you can also import sql/poles.sql manually).
  • Check that the pole’s spawn_prop is 1. A pole saved with Spawn prop turned off is a dance spot only — no prop is spawned, but the interaction and dance still work.
  • Enable Config.Debug to print diagnostics and draw target debug polygons so you can confirm the zones exist.

​
The prop looks wrong or won’t appear

The pole prop is fixed to prop_strip_pole_01 — the only stripper-pole prop that reliably works in GTA 5. It is used for both the placement preview and the spawned prop, and can’t be changed. If placement reports the model is invalid, verify your game files aren’t missing base props.

​
A job lock isn’t applying

  • Make sure the pole was saved with the job lock enabled and a real job selected — the server only honours a job lock when a valid job name is supplied.
  • Job matching uses the framework this resource detected (ESX / QBCore / QBox). Confirm the player’s job name matches the pole’s job exactly.
  • For standalone servers or when the framework can’t supply a job list, populate Config.Jobs so the job appears in the dropdown.

​
Still stuck?

See Support for how to get help.