A QBCore commission should fit the version and conventions of the server you actually run. Jobs, permissions, player data, and integrations all depend on that starting point.
Build around your installed QBCore stack
Share your core version and any changes to it, along with inventory, targeting, menus, and interaction resources. Custom jobs, activities, interfaces, and economy systems can then be designed around the right data and integration points.
Extend systems without creating avoidable overlap
The scope should identify which resource owns each feature and how new behavior interacts with existing scripts. Changes to callbacks, events, item definitions, or saved data need to be made across the affected resources rather than leaving partially migrated systems.
Questions about this service
Can you modify an existing QBCore resource?
Yes, where the source and license permit the work. Provide the resource version, your current changes, and a clear example of the behavior you want.
Is QBCore support the same as Qbox support?
No. Similar concepts do not guarantee identical APIs or resource compatibility. Qbox support should be included and tested separately when a commission needs both.