# Dependencies > Required and optional dependencies for ML HealthSystem Category: HEALTH SYSTEM · Source: https://miciomods.it/docs/ml-healthsystem-dependencies · Last updated: 2026-07-09 ## Required ML HealthSystem declares three hard dependencies in `fxmanifest.lua`. The resource will not start if any are missing. - `ml_bridge`: Framework abstraction layer. Resolves player data, inventory operations, notifications, and usable-item binding without framework-specific exports. - [ox_lib](https://github.com/communityox/ox_lib): Callbacks, zones, context menus, and notifications. - [oxmysql](https://github.com/overextended/oxmysql): MySQL driver. Used for the three persistence tables (`ml_healthsystem`, `ml_lifepoints`, `ml_health_tents`). **fxmanifest.lua** ```lua dependencies { 'ox_lib', 'oxmysql', 'ml_bridge', } ``` ## Framework `ml_bridge` supports QBCore, QBox, ESX, and standalone. Pick the matching tab and add the `ensure` block to `server.cfg`. Load order matters: `ml_bridge` must start after the framework core and before `ml_healthsystem`. **QBCore** **server.cfg** ```cfg ensure qb-core ensure oxmysql ensure ox_lib ensure ml_bridge ensure ml_healthsystem ``` **QBox** **server.cfg** ```cfg ensure qbx_core ensure oxmysql ensure ox_lib ensure ml_bridge ensure ml_healthsystem ``` **ESX** **server.cfg** ```cfg ensure es_extended ensure oxmysql ensure ox_lib ensure ml_bridge ensure ml_healthsystem ``` **Standalone** **server.cfg** ```cfg ensure oxmysql ensure ox_lib ensure ml_bridge ensure ml_healthsystem ``` > **INFO:** Auto Detection > > `ml_bridge` detects the running framework at startup. No framework setting exists in the ML HealthSystem config. The same build runs on QBCore, QBox, ESX, or standalone without edits. ## Inventory Item use, removal, and metadata route through `ml_bridge`. The shipped item definitions target ox_inventory: paste the 29 entries from `_INSTALL/ox_items.txt` (28 medical items plus `respawn_tent`) into `ox_inventory/data/items.lua`. Item keys must match `shared/config/items.lua` and `Config.RespawnTent.Item` exactly, the script binds "on use" via `Bridge.BindUsableItem` against those keys. > **WARNING:** Item key parity > > Renaming an item in `ox_inventory/data/items.lua` without updating the matching key in `shared/config/items.lua` (or `shared/config/respawn.lua` for the tent) breaks the bind. The item will exist in the inventory but do nothing on use. ## Database `oxmysql` is required because ML HealthSystem persists state across three tables, all created automatically on first start via `CREATE TABLE IF NOT EXISTS`: - `ml_healthsystem`: aggregated medical state per identifier (`health_data` LONGTEXT). Live injuries, bleeding, fractures, and diseases are tracked in real time during a session; this table is the persistence layer that survives disconnects and restarts. - `ml_lifepoints`: Life Points balance per identifier. Created only when `Config.LifePoints.Enabled` is true. - `ml_health_tents`: placed respawn tents (coords, heading, optional label). No manual SQL import is needed. ## Optional - [pma-voice](https://github.com/AvarianKnight/pma-voice): Proximity voice muting on death and last stand. Controlled by `Config.Voice` in `shared/config/effects.lua` (`Enable`, `System = 'pma-voice'`, `MuteDead`, `MuteLastStand`). Leave `Config.Voice.Enable = false` to skip it.