AWSAWS DOCUMENTATION38 source-matched resource guides
Documentation/Interface/AWS Multicharacter & Spawn Selector
Interface4 min readUpdated 2026-10-15
AWS Multicharacter & Spawn Selector cover

AWS Multicharacter & Spawn Selector

A character-selection and spawn interface with framework adapters, character slots and configurable appearance/housing integrations.

Installation

Requirements

  • oxmysql
  • One supported core: ESX, QBCore or Qbox
  • A supported appearance resource and any housing/spawn integrations enabled by your configuration

Startup order

This example selects one framework and target. Use the resources matching your configuration and start dependencies first.

ensure oxmysql
ensure qb-core
ensure illenium-appearance
ensure aws-multicharacter

Setup steps

  1. Disable competing multicharacter resources before testing this one.
  2. Back up character/player tables and import sql.sql. The rio_multicharacter_slots table name is intentionally retained so existing slot records continue to work.
  3. Review shared/config.lua framework, identifier and slot settings. Preserve Config.Prefix when upgrading an existing ESX character database.
  4. Review starter items, appearance selection and housing callbacks before permitting character creation/deletion.

Gameplay and usage

  1. Test character creation, selection, disconnect/reconnect and /logout with a test account.
  2. Test ordinary-player restrictions separately from the staff slot-management commands.
  3. Keep Config.Debug disabled for public use after completing integration checks.

Configuration

  • shared/config.lua: Config.Framework selects AUTO, ESX, QBCore or QBox.
  • Config.Characters, Config.Prefix, Config.Identity and Config.StarterItems control character data and creation.
  • Config.ForceAppereance selects appearance integration; Config.Locations and SpawnCoords configure entry points.
  • Config.Commands includes logout, setcharacterslots and addcharacterslots; Config.CommandGroupAllowed limits administration.
  • RIO_UI and RIO_UIV2 remain optional external integration names, rather than bundled AWS resources.

Exports and integrations

  • aws-multicharacter.GetConfigValue — see aws-multicharacter/client/cl_baseevents.lua for its arguments and client/server context.
  • aws-multicharacter.GetUserStorage — see aws-multicharacter/client/cl_baseevents.lua for its arguments and client/server context.
  • aws-multicharacter.CanSwapCoords — see aws-multicharacter/client/cl_baseevents.lua for its arguments and client/server context.
  • aws-multicharacter.Logout — see aws-multicharacter/client/cl_baseevents.lua for its arguments and client/server context.
  • aws-multicharacter.SetLocationsDisabled — see aws-multicharacter/client/cl_baseevents.lua for its arguments and client/server context.
  • aws-multicharacter.isInMulticharacter — see aws-multicharacter/client/framework/framework_functions.lua for its arguments and client/server context.
  • aws-multicharacter.Initialize — see aws-multicharacter/client/functions/world.lua for its arguments and client/server context.
  • aws-multicharacter.isInMulticharacter — see aws-multicharacter/server/framework/framework_functions.lua for its arguments and client/server context.
  • aws-multicharacter.Logout — see aws-multicharacter/server/functions/characters.lua for its arguments and client/server context.
  • aws-multicharacter.IsReady — see aws-multicharacter/server/sv_main.lua for its arguments and client/server context.
  • aws-multicharacter.GetFramework — see aws-multicharacter/server/sv_main.lua for its arguments and client/server context.
  • aws-multicharacter.GetFrameworkProfile — see aws-multicharacter/server/sv_main.lua for its arguments and client/server context.

Troubleshooting

  • Infinite selection/loading: review core/appearance startup order and server integration logs.

  • Missing characters or slots: check framework identifiers, ESX prefix and the existing slot table.

  • Incorrect spawn or housing: review the selected location and housing adapter before changing player data.

  • Include the package version, framework and exact server/F8 error when requesting support. Remove private tokens and player data.

Package reference

Manifest Version
fxmanifest.lua 1.0.1

Database files

  • aws-multicharacter/sql.sql

Configuration reference

  • aws-multicharacter/server/errortracker/modules/config_multichar.lua (edit the table returned/defined by this file).
  • aws-multicharacter/shared/config.lua: Cameras, Filters, DefaultSettings, Effects, SphereIntensity, SphereColor, Debug, CheckIntegration, IssueHelper, DebugTimers, Framework, Prefix, ForceAppereance, AutoHandleUIV2, UseMusicFromUIV2, UserInterface, Characters, ServerLogo
  • aws-multicharacter/shared/config_framework.lua (edit the table returned/defined by this file).
  • aws-multicharacter/shared/config_locations.lua: Locations
  • aws-multicharacter/shared/config_usersettings.lua: Filters, Cameras

Frequently asked questions

Does this need Keymaster or an escrow key?

The Lua sources in this delivery package were readable in the static audit. No /assetpacks requirement is added by this package. Required framework, inventory and map resources still need to be installed separately.

Can I change the folder or database table names?

Keep the supplied folder names. Historical event, SQL and KVP identifiers are retained to protect existing integrations and saved data. Renaming a table or event requires a separate migration.

Why is an interface or item missing?

Check the startup order, selected framework/target adapter, inventory item definitions and the server/F8 console. The package does not install an entire framework or inventory for you.

Has this been tested on my server?

ZIP integrity, source readability, script syntax and manifest references were checked locally. Multiplayer gameplay, your framework version and integrations require a FiveM server acceptance test before a public release.