Skip to main content

wasabi_multichar

We’ve always aimed to be the go-to alternative to framework-specific multicharacter, registration, and spawn systems. With wasabi_multichar (v2), we rebuilt that experience from the ground up - keeping what people loved, but making it more stable, reliable, and easier to expand moving forward.

danger

The resource folder must be named wasabi_multichar or the resource will not operate correctly.

Features​

  • Multi-framework support - Automatically detects and bridges ESX, QBCore, QBOX, or a custom framework bridge.
  • Modern character selection UI - React/NUI powered selection flow with character stats, creation, deletion, and slot purchase prompts.
  • Configurable character slots - Set a base maximum slot count and add extra VIP slots by database/webstore flow or admin command.
  • Configurable intro and UI color - Tune the welcome camera, first-open intro delay, and UI accent color from client config.
  • Debug/update controls - Enable verbose debug logging and built-in update checks from config when needed.
  • Built-in character registration - Create new characters directly from the multichar interface.
  • Character deletion controls - Allow or disable deletion globally, with optional ACE restriction for deletion permissions.
  • Preview locations - Configure cinematic character preview scenes with cameras, peds, animations, props, IPLs, interiors, and optional spawned vehicles.
  • Spawn flow options - Spawn at last position, default coords, job-based fallback coords, or hand off to a custom spawn selector.
  • Appearance bridge - Loads saved character appearance for supported clothing/appearance resources through bridge files.
  • Webstore/VIP slot support - Optional Tebex package confirmation and webstore link support for additional slots.
  • Logout support - Configurable logout command to return players to character selection, with optional staff-only restriction.
  • Locale support - Locale files are loaded from locales/*.json for UI/server strings.

Supported frameworks​

  • ESX
  • QBCore
  • QBOX
  • Custom bridge fallback

The active framework is detected from resource state checks in the bridge files. Config.Framework is informational and does not force a bridge by itself.

Main configuration areas​

AreaFilePurpose
Shared configconfig/shared/config.luaCharacter slots, deletion, spawn options, job spawns
Client configconfig/client/config.luaWelcome camera, nationalities, character stats, webstore link
Server configconfig/server/config.luaFramework info, logout command, VIP command, Tebex package, starter items
Preview scenesconfig/client/previewLocations.luaCinematic cameras, ped slots, animations, props, IPLs, vehicles
Bridgesbridge/**Framework, appearance, notify, and spawn integration hooks

Preview​