Framework Integration

To ensure your server's core recognizes the Boyraz Multicharacter as the primary character management system, a few lines of configuration must be updated. This prevents native logic from interfering with our custom UI.

---

🟦 ESX Legacy Integration

For ESX-based servers, you need to tell the framework that a custom multicharacter resource is active.

File Path: es_extended/shared/config.lua

Locate the Config.Multichar setting and update the detection logic:

-- Find and replace the Multichar configuration:
Config.Multichar = GetResourceState("uz_Multicharacter-2") ~= "missing"

Pro Tip: This single line ensures that ESX automatically detects our resource and initializes the player data seamlessly without triggering its default UI.

---

🟩 Qbox Core Integration

Qbox handles external resources via its internal config. You must disable the core's built-in character management to allow Boyraz Multicharacter to take full control.

File Path: qbx_core/config/client.lua

Find the characters section and update the following settings:

-- Update these variables inside the config:
useExternalCharacters = true,    -- Disables the core's internal character management
startingApartment = false,       -- Prevents native apartment UI overlap
enableCharacterCreator = false,  -- Routes character creation to the Boyraz system

---

✅ Verification Steps

After applying these modifications:

1. Save all edited files.

2. Restart your server or the core resources.

3. Observe the server console to ensure there are no framework-specific initialization errors.

4. The framework should now stay idle until the Boyraz Multicharacter UI triggers the player load event.

Maintenance Note: If you update your es_extended or qbx_core resources to a newer version in the future, these manual changes may be overwritten. Keep a record of this step.