Install
Requirements, load order and what happens on the first start.
The steps are the same for all four resources. ktx_garages stands in for the name below.
Requirements
| oxmysql | database access |
| ox_lib | notifications and the prompt on screen, plus the callbacks in ktx_garages |
| MySQL or MariaDB | the tables are created on the first start |
| OneSync | has to be on |
Steps
- Buy the resource in the store, then download it in the Cfx.re portal.
- Put the folder into your
resourcesdirectory. - Start it after its dependencies:
ensure oxmysql
ensure ox_lib
ensure ktx_garages- Open the config file and set
Config.Framework.name, see Frameworks. - Restart the server.
Every table a resource needs for itself is created when it starts for the first time, so there is no schema to import.
ktx_cases and ktx_fishing need one step more. Their items live in your inventory, and nothing can be opened or caught before they exist there:
| ESX and QB-Core | import items/esx_qb.sql |
| ox_inventory | paste items/ox_inventory.txt into ox_inventory/data/items.lua |
Both folders carry a README with the full item list. See Cases items and Fishing items.
ox_lib and oxmysql have to run before the resource, not after. A resource that starts without an error and then does nothing is usually a load order.
Where the config sits
| ktx_garages | shared/config.lua |
| ktx_fishing | config.lua |
| ktx_dispatch | config.lua |
| ktx_cases | config.lua |
Every block in there carries a comment above it. The settings page of each resource shows the same file on the website.