> For the complete documentation index, see [llms.txt](https://tg-dev.gitbook.io/tg-dev-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tg-dev.gitbook.io/tg-dev-docs/tg-cornerselling/troubleshooting.md).

# Troubleshooting

### Troubleshooting

#### The resource does not start

* Confirm `ox_lib`, `oxmysql`, `community_bridge`, and OneSync are available.
* Confirm dependency start order.
* Check the FXServer console for config checker output.
* Check the `oxmysql` connection.
* Fix every config error shown in the server console.

#### The player cannot open `/cs`

* Check `BlockedJobs`.
* Check `JobOnly` and `AllowedJobs`.
* Check `ACEOnly` and `ACEPermission`.
* Confirm the framework reports the player's job and loaded state correctly.
* Confirm the database initialization completed.

#### A player cannot start selling

* The player must be inside a configured area.
* The profile must not be blocked by an administrator.
* The minimum police requirement must be met.
* The area must contain at least one buyer.
* The buyer pool must have an available buyer.
* The global or area operation must not be paused.

#### Items do not appear

* Confirm the item exists in the inventory.
* Confirm its name matches `Config.Items`.
* Confirm it appears in the selected area's `items` list.
* Confirm the player meets `minLevel` and `minRep`.

#### Item images do not load

* Confirm `ItemImagePath` points to the correct inventory image folder.
* Keep `%s` in the path so the item name can be inserted.
* Confirm the PNG filename matches the item name.
* Set `ItemImagePath = ''` if your inventory bridge already returns a valid image.

#### Dispatch does not arrive

* Confirm `Config.Dispatch.Enabled = true`.
* Confirm the selected dispatch resource is started.
* Try `System = 'auto'` to use detection and built-in fallback.
* Confirm the police job names match `Config.Dispatch.Jobs`.
* For built-in dispatch, confirm those players are loaded and have one of the configured jobs.

#### Admin prices do not survive a restart

* Confirm the FXServer process can write to the resource folder.
* Confirm `config/price_overrides.lua` exists.
* Check the server console and external system logs for a price persistence error.

#### External logs do not work

* Confirm `Config.Logs.Enabled = true`.
* Confirm the selected log system is correct.
* For Discord, confirm the webhook convar is set.
* For FiveManage, confirm `FIVEMANAGE_LOGS_API_KEY` is set and `fmsdk` starts first.

### Notes for Resource Developers

* Client and server exports are the supported integration surface.
* Internal callbacks and network events are implementation details and may change.
* Sale rewards, prices, items, permissions, and progression should remain server-authoritative.
* If another resource grants XP, reputation, or Heat, call the provided server exports from a validated server action.