Skip to main content
HumaLike selects each integration domain independently. Installing a framework does not force its inventory or interaction system.

​
Built-in priorities

​
Player

​
Inventory

​
Interaction

The ESX inventory is deliberately a fallback, so ox_inventory wins when both are available. If ox_inventory and qb-inventory, or ox_target and qb-target, run together at the same priority, select one explicitly.

​
Jobs and duty

  • QBCore and Qbox require job.onduty == true when an interaction requires duty.
  • ESX has no universal duty field. Membership passes unless the server’s job object explicitly exposes a false onduty or onDuty value.
  • Standalone has no job system. Empty job requirements pass and configured job requirements fail until a custom player provider implements HasJob.

​
Runtime changes

Starting, stopping, or restarting a framework, inventory, target, or custom bridge causes provider selection to be evaluated again. HumaLike does not need a full server restart. Run humalike_status after changing resources. Resolve ambiguous, unavailable, or degraded domains before testing gameplay.

​
Custom or modified frameworks

Built-in providers support the public behavior of the listed frameworks. A heavily modified fork may expose different exports, player data, duty state, or events. Connect it through a custom bridge instead of editing HumaLike.

​
Next