How mitlight/es_extended works
es_extended is a FiveM roleplay framework whose documented player-facing capabilities include accounts, inventory, jobs, and persistent loadouts and positions. The graph separates server and client runtime, browser UI, and shared localization; it also shows the documented database dependency. Source excerpts are limited to the browser UI and message wrapper, so most gameplay relationships are documented at the capability level rather than traced through server calls.
Main entry points: player.lua Player state · server Loadout & position · client/main.lua Client runtime · server/main.lua Server runtime
Components 21
Server gameplay
- Player state
server/classes/player.lua - Accounts
server - Inventory
server - Jobs
server - Loadout & position
server - Server runtime
server/main.lua
Client runtime
- Client runtime
client/main.lua - Client functions
client/functions.lua - Entity iteration
client/entityiter.lua - Death handling
client/modules/death.lua - Scaleform UI
client/modules/scaleform.lua - Asset streaming
client/modules/streaming.lua
Browser UI
- HUD & notifications
html/js/app.js - Message wrapper
html/js/wrapper.js
Shared services
- Localization lookup
locale.js - Translation catalogs
locales - SQL schema
es_extended.sql
Other components
- Roleplay player
- FiveM runtime
- MySQL database
- EssentialMode
Connections 11
- Roleplay player → Client runtime: plays through
- Client runtime → FiveM runtime: runs in
- Server runtime → EssentialMode: extends
README.md - Player state → Accounts: has accounts
README.md - Player state → Inventory: uses inventory
README.md - Player state → Jobs: has job
README.md - Player state → Loadout & position: syncs state
README.md - Loadout & position → MySQL database: persists to
README.md - SQL schema → MySQL database: defines schema
README.md - HUD & notifications → FiveM runtime: receives messages
html/js/app.js - Message wrapper → FiveM runtime: posts chunks
html/js/wrapper.js