βš™οΈConfiguration

Multicharacter TriggerEvent : 0bug_Multicharacter:start

-- From Server Side: 
TriggerClientEvent('0bug_Multicharacter:start', source)

-- From Client Side:
TriggerEvent('0bug_Multicharacter:start')

For ESX Go to es_extended/shared/config/main.lua configuration and make sure you have these 2 options set to true'

Config.Multichar                 = true
Config.Identity                  = true

For QBox Go to client -> config.lua and make sure you have this option set to true.

useExternalCharacters = true

Basic Settings

Customize = {
    DefaultCharSlot = 10,         -- Maximum character slots by default
    Rules = true,                 -- Enable/disable rules acceptance
    Lang = "en",                  -- Language setting (en, fr, es, etc.)
}

Character Management

Character Creation Rules

Spawn System

Framework-Specific Settings

LoadHouse should be set to true if you use our Spawn Selector V2 and enabled spawning at your own house.

Starter Items

Load Character Custom Code

Custom Clothing Script

Open this Paths in your visual studio code

  • 0bug-core/client/Clothes

  • 0bug-core/server/Clothes

Add in every part of the code an elseif condition for your custom script and add your exports and triggerevents then adapt them with the existing provided data in each function .

You can take example of how we did with multiple pre-configured clothing scripts in there to have a better look and idea with the help of your custom clothing script providers if you don't have enough coding knowledge.

Music System

Scene Creation Mode

Translations

All translations are under the locales/en.lua file

Framework Configuration Guide

If you're using a different framework path/name (e.g., np-core instead of qb-core), you'll need to modify the threads.lua file in 0bug-core:

  1. Open 0bug-core/threads.lua

  2. Locate the GetFramework() function

  3. Modify the export paths according to your framework:

Important Notes

  1. Always backup your configuration before making changes

  2. Restart the resource after modifying the config

  3. Test changes in a development environment first

  4. Make sure all coordinates are valid for your server

Last updated