FiveM Docs
Core Resources

Core Resources

Overview of every ESX Legacy 1.16.4 core resource in [core], what each one does, which are required, and the recommended ensure order for server.cfg.

The [core] folder of ESX Legacy contains es_extended plus a set of small resources that provide the UI, character creation, inventory and utilities the framework relies on. This page lists every core resource in ESX Legacy 1.16.4, what it does and whether you can remove it.

Resource overview

ResourcePurposeSideRequired?
esx_libShared library (xLib): callbacks, streaming, points, validation, SQL catalogSharedYes, es_extended depends on it
es_extendedThe framework itself: players, jobs, accounts, itemsSharedYes
esx_notifyToast notifications behind ESX.ShowNotificationClientYes in practice
esx_textuiPersistent prompt behind ESX.TextUIClientYes in practice
esx_progressbarTimed progress bar behind ESX.ProgressbarClientYes in practice
esx_contextMouse context menus and small forms (ESX.OpenContext)ClientYes in practice
esx_menu_defaultClassic keyboard menu (ESX.UI.Menu, type default)ClientNeeded by most addons
esx_menu_dialogText and number input dialog (type dialog)ClientNeeded by most addons
esx_menu_listTable-style list menu (type list)ClientNeeded by some addons
skinchangerApplies ped model, clothes and face dataClientYes, ESX.SpawnPlayer waits for it
esx_skinCharacter appearance editor and skin storageSharedYes for character creation
esx_identityRegistration form: name, date of birth, sex, heightSharedYes for character registration
esx_multicharacterCharacter selection with several slots per playerSharedNo
esx_inventoryDefault slot inventory and storagesSharedUnless you use ox_inventory
esx_whitelistIdentifier or Discord-role whitelist with admin panelSharedNo (disabled by default)
esx_loadingscreenLoading screen while connectingClientNo
esx_chat_themeVisual theme for the cfx chat resourceClientNo
cronDaily scheduled tasks via cron:runAtServerOnly for addons that use it (esx_society, esx_vehicleshop)

Yes in practice

es_extended does not list these as manifest dependencies, but its client functions call them directly. If one of them is missing, ESX.ShowNotification, ESX.TextUI, ESX.Progressbar or ESX.OpenContext throws Resource [name] is Missing!.

The official txAdmin recipe starts the core like this:

server.cfg
ensure chat
ensure oxmysql
ensure esx_lib

ensure es_extended
ensure [core]

ensure [standalone]
ensure [esx_addons]

ensure [core] starts every resource in the folder. Each resource declares its dependencies in fxmanifest.lua (for example esx_multicharacter depends on esx_context, esx_identity and esx_skin), so FiveM starts them in a valid order. If you list resources one by one, follow the dependency order:

server.cfg
ensure chat
ensure oxmysql
ensure esx_lib
ensure es_extended
ensure cron
ensure esx_notify
ensure esx_textui
ensure esx_progressbar
ensure esx_context
ensure esx_menu_default
ensure esx_menu_dialog
ensure esx_menu_list
ensure skinchanger
ensure esx_skin
ensure esx_identity
ensure esx_multicharacter
ensure esx_inventory
ensure esx_whitelist
ensure esx_loadingscreen
ensure esx_chat_theme

Leave out the optional resources you do not use. See server.cfg for the full file.

Explore the core resources

Frequently asked questions

Independent documentation

esx-fivem.com is a community project and is not affiliated with the ESX Framework team. Facts on this page were checked against the upstream source. Official resources: docs.esx-framework.org and github.com/esx-framework.
Edit on GitHub

Last updated on

On this page