Connect ERS callouts to the framework around them.
ers_integration bridges Emergency Response Simulator activity into QBCore server systems. The current manifest and scripts call qb-core directly, so Qbox installations need a compatible QB bridge exposed as qb-core. Installation requires ERS plus coordinated PS Dispatch, radial-menu, target, and database setup.
Back up PS Dispatch and radial-menu configuration before making integration edits.
Apply the provided alert and radial-menu entries from the INSTALL ME folder.
Place ers_integration in your resources and import INSTALL ME/SQL/ers_database.sql.
Configure duty locations, dispatch timing, rewards, notifications, inventory, and target behavior.
ensure ox_lib
ensure oxmysql
ensure qb-core
ensure nearest-postal
ensure ps-dispatch
ensure ox_target # or qb-target
ensure qb-radialmenu # or qbx-radialmenu
ensure night_ers
ensure ers_integrationCreate backups of PS Dispatch and radial-menu configuration before applying any provided alert or menu entries.
Use the matching files in the INSTALL ME directory for dispatch alerts and the selected qb or qbx radial menu.
Import INSTALL ME/SQL/ers_database.sql before testing MDT profiles, vehicles, calls, reports, personnel, services, dispatch, and history features.
Configure duty locations, dispatch delays, rewards, notifications, inventory options, target behavior, jobs, and access rules for the chosen framework.
Arrival and traffic-stop bonuses are marked as potentially exploitable. Restrict or disable them as needed, and use a quoted deposit type such as 'bank' or 'cash'.
Config.BonusPayDepositType = 'bank'Verify duty access, a traffic stop, an ERS callout, a pursuit, service requests, dispatch arrival, radial actions, target actions, and MDT persistence with the intended jobs.
/togglecrosshairEmergency Response Simulator is not included with this bridge. Install and validate the required Nights Software resource separately.
Confirm PS Dispatch is running, the supplied alert additions were applied to the correct version, and the configured event names were not changed.
Confirm the configured qb or qbx radial resource and supported target system start before the integration, then review job and duty restrictions.
Confirm the included SQL was imported, oxmysql is started, and the server console reports no schema or query errors.
Validate night_ers first, then confirm qb-core—or a compatible bridge exposed under that name—is running and provides the QBCore API expected by the integration.