Installed by the developer.
Buy a script, add the installation, and the person who wrote it puts it on your server. Or bring a framework that is not on the list.
Installation
One KTX resource installed on your server by the developer, started on your framework and tried in the game before it is handed back.
Included- Install - The resource is placed, its dependencies are checked, and the start order in your server.cfg is set.
- Framework - Config.Framework is set to what you run, the bridge is checked against your framework version, and a renamed table or column is mapped in the config.
- Your settings - Prices, spots, garages or services go into config_local.lua, so the next update leaves them untouched.
- Tried in the game - Every feature of the resource is used once on your server before the ticket is closed.
- Access - Read access to the server files and a database user for the duration. Nothing else is touched, and both can be revoked afterwards.
- Changes welcome - Want a feature the script does not have, or a flow that works differently on your server? Say so in the ticket. Adapting the script to your server is part of the work.
Framework adapter
A bridge adapter written for a framework that is not on the list, so a KTX resource runs on it the way it runs on ESX, QB-Core, QBox and ox_core.
Included- One adapter per resource - It answers the functions listed in bridge/INTERFACE.md of that resource and nothing else.
- Outside escrow - The adapter goes into public/framework.lua, which is readable and yours to change.
- Your framework - Identifiers, jobs, money, items and vehicles are read from and written to your framework, not to a copy of it.
- Tried on your server - Every required function is used once in the game before the adapter is handed over.
- Updates - The file is never replaced by an update, so the adapter survives every release of the resource.
- Changes welcome - Want a feature the script does not have, or a flow that works differently on your server? Say so in the ticket. Adapting the script to your server is part of the work.
Buy
The service goes into the cart next to the script, or on its own.
Ticket
Open a ticket in Discord with your server and what you bought.
Done
The developer does the work on your server and closes the ticket when it runs.
Want the script to do something it does not? Open a ticket and ask. A feature, a different flow, a change for your server: that is part of the work.
Open Discord