Installation

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

FiveM Asset Escrow System

Asset dependencies

This asset only has one mandatory dependency, a compatible clothing system or that you make it compatible.

Remember to delete the following assets according to the dialog boxes below.

In case of esx version

In the case of esx version we only have to eliminate the esx_multicharacter.

In case of qbcore version

In case of qbcore version, we will have to eliminate qb-multicharacter and qb-spawn, the latter only in case you want to use the spawn selector that includes the asset (yes, it is compatible with qb-apartments if you enable it in the fxmanifest. qs-multicharacter lua)

This asset is compatible with the clothing systems named below, if you have another, you can make the compatibility yourself or ask the creator, since it has open source files with multiple examples within the asset.

Remember that if your clothing is run replacing esx_skin and skinchanger, it will possibly work without prior edits, simply by declaring esx_skin or qb-clothing in the config.

This asset is automatically compatible with the following systems

qb-clothing

esx_skin

illenium-appearance

I use illenium-appearance and spawn without my correct clothes/body

In case when you spawn you do not appear with the correct clothing or appearance, here is the solution. If not, create a completely new txadmin base and install as explained in the official illenium-appearance docs.

  1. Go to your illenium-appareance and open the manifest, look for the lines that say provides {esx_skin, skin_changer} and proceed to remove them.

  2. Look in your scripts if the following line exists in the manifests dependencies{esx_skin, skin_changer} and remove it.

  3. Clear cache and restart your server.


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.

This asset is not dependent on other scripts, therefore we only have to place it under our framework for its correct functioning.

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

-- Place it right below your framework
ensure [multicharacter] or qs-multicharacter

Database

This asset installs its database automatically.

Quasar Multicharacter has an intelligent system that will create the database for you, so it does not require a database installation or modification by you. If you are interested in the information, the table is called multichar_slots.


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