Installation | Quasar Store Documentation

Welcome to the Quasar Smartphone PRO 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.

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.

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

If you have more problems regarding , 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.

Asset dependencies

READ CAREFULLY: We strongly recommend NOT USING phpmyadmin. Use and the most stable version of .

To use this asset you must have gamebuild version 2545 or higher. If you do not complete this step, you will never be able to open or start the phone.

How to update the game build to version 2545?

This is a very simple step, we will directly access the artifacts for or , depending on our type of server. We will download it and replace it with the artifacts from our server.

Once this step was done, they added sv_enforceGameBuild 2545 in your server.cfg, make sure you don't have another convar with the same name or another version.

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.

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 execution of this asset, we will respect the respective order mentioned below. We recommend starting both dependencies and the same smartphone asset in the same [smartphone] folder. Otherwise we will have to start the dependencies first and then the qs-smartphone-pro.

Database

Our Smartphone PRO system includes multiple databases, which will require you to wipe your current databases on other phones.

Before running the Smartphone PRO we will have to update and install our database, select the option that suits your framework since each one is different.

Database for esx

This database is exclusive for esx, if you do not use said framework, look for the next part of this document. This event will remove your current data and install the new ones completely.

Database for qbcore

If you are a qbcore user, you will also need to edit the playertables of your qb-core, removing the tables from the old qb-phone, if you use the default tables in your qb-core/server/player.lua, you can simply copy and paste this to edit your playertable.

This database is exclusive for qbcore, if you do not use said framework, look for the next part of this document. This event will remove your current data and install the new ones completely.

Items for Smartphone use

This asset has different items with different uses or phone colors. If your inventory file is not located here, you can take another one as an example and simply adapt it to your needs.

If you use qbcore + ox_inventory, you must add the items inside ox_inventory for the phone opening to work.

Smartphone has a series of items that are important for its use. For example, phones with different colors or simply items that will apply new functions to our new phone.

Here you will find a series of selected items in different extensions for different inventories, select the option that suits your server, remember that Quasar Store has a completely unique Inventory system with which you can also enjoy your phone.

Items for qs-inventory

Items for origen_inventory

Next, to show the item information with its metadata, we will search in origin_inventory/html/js/app.js and edit the function called FormatItemInfo.

We will place the following code right on the first line within this function:

Then below we can add this code to give metadata to all the items of the Smartphone PRO:

The result should look like this:

Items for qb-inventory

To reproduce the item information with data such as name or phone number, we will have to add this in qb-inventory/html/js/app.js within the generateDescription function.

Don't forget to add this just below the function title, on line one within it. Otherwise you can add the items below one by one, but this way we will save lines of code.

Item for ox_inventory

Items for core_inventory

In core_inventory/config.lua find ItemCategories and add in it:

In the case of core_inventory it varies whether we use esx or qbcore. In case of esx:

In the case of qbcore:

Items for esx_inventory

Unique Phones

If your inventory is not in the list, you can ask the creator of your inventory for help to make the compatibility by sending them the Smartphone PRO files to make it compatible.

If you do not use any of these inventory systems, you can still use the phone but without metadata on the item and the phones will not be unique.

The unique telephone system will work automatically if you use any of the inventory listed below, if yours is not listed, you will automatically have no unique phones.

In case your inventory is not listed, you can edit the config.lua using Config.UniquePhone and Config.Inventory, adding more values on the client/custom and server/custom side, which are open source so you can edit yourself these values if you have the necessary knowledge.

Voice system & configuration

If you use a voice other than pma, mumble, toko or salty, you can edit them in client/custom/voice or server/custom/voice.

If you renamed your voice, you will have to edit the export names in client/custom/voice or server/custom/voice.

To configure the voice, we will simply go to config.lua and in Config.Voice we will select the voice we want to use as follows. If you use another one, edit it yourself in the client or server custom folders.

Photos, videos & webhooks

Do not run the asset or open a ticket without first completing this step.

You must also add the token or webhook in the qs-videos/config/config.js asset.

Due to the new terms of Discord, many servers will no longer be able to use the webhooks that were usually used, so we recommend using fivemanage.com, within the following sliding box, you will find a guide on how to create the token and use it. of the.

Option via fivemanage.com

Option via webhook (Not working at this time)

To add the webhooks to this asset, we will have to go to qs-smartphone-pro/server/custom/webhooks, there we will find the configurable ones to add the webhooks.

If you skip this step, you will not be able to take photos or videos on the phone, avoid skipping this step before opening a ticket in the community.

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.