Installation

Welcome to the Quasar Billing installation guide, here you can learn how to completely install our asset, following each step we will achieve a clean and fluid installation where you will not find any problems, as long as the documentation has been completed in full.

If you do not have programming experience, we recommend that you read each step completely without skipping any lines, since all documentation is important and should not be ignored under any circumstances. If you have a trusted developer, you can install this quickly, easily and safely if you complete this documentation step by step.

If at the end of this documentation you still have any problems, review each step again, after having checked that everything is correct, you can obtain more information about common errors in the Common Problems section within this same documentation to seek help independently.

Asset download

To find the asset, you must have made the purchase using your own keymaster account. Otherwise, you can use the transfer system to move the asset to a different keymaster account.

If you need to make an update you must also do this step again, download the asset and you will get the complete update.

Once the purchase is made on our official website, you will receive your asset directly in your Keymaster, in your own panel you can download the asset and install it following the following documentation.

If you have more problems regarding Fivem Escrow, accounts or asset startup errors you can go here and see if any of them match your case, since Escrow requires some basic things for its operation, such as your keymaster account, your licensekey , etc.

pageFiveM Asset Escrow System

Asset dependencies

If you use esx you will have different dependencies than when using qbcore, pay attention.

This asset has mandatory dependencies and optional dependencies, it also varies if you use qbcore or esx. Please read the dependencies carefully to understand better.

This asset has some dependencies that are completely mandatory and important for the operation of the asset. If you do not have these dependencies, your asset will probably start and have some error or message in its command console.

Dependencies	Direct links
ox_lib	https://github.com/overextended/ox_lib/releases

Dependencies

Direct links

ox_lib

https://github.com/overextended/ox_lib/releases

As optional dependencies we will have two options, for esx or qbcore, these are optional because they are used if we want to use companies and management.

Optional dependencies for qbcore

qb-menu

https://github.com/qbcore-framework/qb-menu

qb-management

https://github.com/qbcore-framework/qb-management

Optional dependencies for esx

esx_addonaccount

https://github.com/esx-framework/esx_addonaccount

Asset positioning

Correctly position the assets by following this step, if something goes wrong you will probably get errors about exports not found, do not skip this step.

For the correct execution of the asset, we will put the asset and its dependencies inside a folder called [billing], then we will execute it completely using ensure as in the example.

The starting order is not very important in this asset, but just in case we will leave the basics so as not to receive general errors when using it. Always respect the framework and inventory above this asset.

-- First we will start the cores, never below
ensure es_extended or qb-core

-- The inventory should be executed above
ensure [inventory]

-- Run qs-billing here along with its dependencies
ensure [billing]

Database

Run this complete sql inside your database to continue with the installation, do not skip this step as it is crucial for the use of the asset we are installing.

The same database will be used in both qbcore and esx.

CREATE TABLE `qs_billing` (
  `id` int(50) NOT NULL PRIMARY KEY AUTO_INCREMENT,
  `receiver_identifier` varchar(255) NOT NULL,
  `receiver_name` varchar(255) NOT NULL,
  `author_identifier` varchar(255) NOT NULL,
  `author_name` varchar(255) NULL DEFAULT NULL,
  `society` varchar(255) NOT NULL,
  `society_name` varchar(255) NOT NULL,
  `item` varchar(255) NOT NULL,
  `invoice_value` int(50) NOT NULL,
  `status` varchar(50) NOT NULL,
  `notes` varchar(255) NULL DEFAULT ' ',
  `sent_date` varchar(255) NOT NULL,
  `limit_pay_date` varchar(255) NULL DEFAULT NULL,
  `fees_amount` int(50) NULL DEFAULT 0,
  `paid_date` varchar(255) NULL DEFAULT NULL
);

Items for Inventories with metadata

This item is optional and will only work with metadata-based inventories.

This system will only work with metadata items, don't worry, you can not use this system if you do not have a compatible inventory or you do not like this function.

Items for qs-inventory

['bill_paper'] = {
    ['name'] = 'bill_paper',
    ['label'] = 'Bill Paper',
    ['weight'] = 0,
    ['type'] = 'item',
    ['image'] = 'bill_paper.png',
    ['unique'] = true,
    ['useable'] = true,
    ['shouldClose'] = true,
    ['combinable'] = nil,
    ['description'] = 'View your invoice'
},

Items for qb-inventory

['bill_paper'] 			 	= {['name'] = 'bill_paper', 							['label'] = 'Bill Paper', 						['weight'] = 10, 		['type'] = 'item', 		['image'] = 'bill_paper.png', 				['unique'] = false, 		['useable'] = true, 	['shouldClose'] = true,	   ['combinable'] = nil,   ['description'] = 'Visa card, can be used via ATM'},

Items for ox_inventory

['bill_paper'] = {
    label = 'Bill paper',
    weight = 1,
    stack = false,
    close = false,
},

Basic asset configuration

We do not recommend editing frameworks unnecessarily, since almost all assets depend exclusively on your framework and exports on the name of your framework. Otherwise and if you edited your framework, read these steps carefully.

If you still require more open codes for the configuration, you can check within client/custom and server/custom to adapt the asset to your personal taste.

Please expand each part to see information about the configuration of the asset, this way you will understand the general operation of the asset on the framework and editable files side.

Basic framework configuration

The asset will work automatically if your framework is called es_extended or qb-core, it will automatically detect if any of them are started. In case your framework has been renamed, you can modify it in config.lua to edit the name of your framework.

Advanced framework configuration

If your framework is completely modified, both in events and name, you should access client/custom/framework or server/custom/framework to adapt the native events of your framework to the codes you have created. If this step doesn't work, we ask that you ask your framework modifier or trusted developer for help.

More general settings

This asset contains multiple configurations within the config folder. But you can also access more open source and configurations within client/custom or server/custom. We do not recommend using these configurations if you do not have the basics of programming.

Last updated 4 months ago