Installation
Last updated
Last updated
Welcome to the Quasar Drugs 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.
For compatibility and security reasons, we request that WinSCP be used mandatorily to manage the script files instead of FileZilla. WinSCP offers greater stability and better integration with our work environment, ensuring a more efficient handling of assets and minimizing issues related to file transfers. We appreciate your cooperation in ensuring a better experience for everyone.
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.
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.
Make sure to install all dependencies before running the asset, always check the meta_libs folder as it could have another file with the same name inside.
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.
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 [drugs], 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.
If you don't have the items integrated correctly, you will receive random errors.
Check that you don't have duplicate items in your inventory or database before integrating them, otherwise you might have some errors.
This asset depends on certain items for its operation, so don't forget to integrate all items correctly into your database or inventory system, depending on how you use your server.
If your inventory is not among the following, you can create the file yourself using the examples of each item by displaying any of the following tabs.
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.
Don't forget to add your vehiclekeys system inside config/seller.lua, in Config.Vehiclekeys.
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.