Installation
1. Requirements
- ox_lib
- oxmysql
- OneSync
- Server artifact 7290 or newer
- One framework: Qbox, QBCore or ESX
2. Add the resource
Put the kyoJobCreator folder in your resources folder and start it after its dependencies, your framework and your inventory:
ensure ox_lib
ensure oxmysql
ensure qbx_core # or qb-core / es_extended
ensure ox_inventory # your inventory
ensure kyoJobCreator
Important: do not escrow or rename the
config/files. They are read withlib.require, which cannot open an encrypted file.
3. Database
Nothing to do. On start, kyoJobCreator applies its own migrations and records them in kyo_schema_version.
sql/install.sql contains the full schema. Import it only if your database user cannot create tables from a resource. Importing it is equivalent to letting the resource migrate.
sql/uninstall.sql removes everything, for a clean reinstall. Make a backup first.
4. Admin access
Every panel feature is an ACE permission. Give everything to your admins in server.cfg:
add_ace group.admin kyo.admin allow
Or grant features one by one; see Permissions.
Tip: opening
/jobcreatorwithout permission shows a screen with the exactadd_aceline for your own identifiers, ready to copy. Turn it off withshowSetupHelp = falseinconfig/server.luaonce your server is set up.
5. First steps
/jobcreator> Import: see the jobs your framework already has. Link or adopt the ones you want to manage here.- Jobs > New job: name, label, type and ranks.
- Open the job > Locations: stand where each point should be and create it.
- Integrations: check what was detected (inventory, target, clothing, billing…).
Diagnostics
| Command | What it shows |
|---|---|
/kyoadapters | Every adapter resolved, and proof the notifications draw |
/kyoclient | What this player’s client resolved |
/kyoprofile | What the server has been doing and what it cost |
/kyostash | Whether the container watcher is alive |
They change nothing. Their extra logging is controlled by debug in config/shared.lua; keep it false on a live server.