Overview
ers_integration connects Emergency Response Simulator (ERS) to a QBCore server. It links ERS with dispatch alerts, a police computer (MDT) and its database, radial-menu actions, and in-game target interactions. Qbox servers need a compatible bridge that provides qb-core, and ERS must be installed separately.
Requirements
- Framework
- QBCore API; Qbox requires a QB compatibility bridge
- Required
- night_ers, PS Dispatch, ox_lib, oxmysql, nearest-postal
- Menu
- qb-radialmenu or qbx-radialmenu
- Libraries
- ox_lib, oxmysql, and a supported target
Installation
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.
Configuration
Back up integration targets
Create backups of PS Dispatch and radial-menu configuration before applying any provided alert or menu entries.
Apply the included integration edits
Use the matching files in the INSTALL ME directory for dispatch alerts and the selected qb or qbx radial menu.
Prepare the database
Import INSTALL ME/SQL/ers_database.sql before testing the mobile data terminal (MDT), including profiles, vehicles, calls, reports, personnel, services, dispatch, and history.
04Tune the server workflow
Configure duty locations, dispatch delays, rewards, notifications, inventory options, target behavior, jobs, and access rules for the chosen framework.
Secure optional bonus payouts
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'How to use and test it
Test every connected system
With the intended jobs, test duty access, a traffic stop, an ERS callout, a pursuit, service requests, dispatch arrival, radial-menu actions, interaction actions, and saved MDT data.
/togglecrosshairTreat ERS as a separate requirement
Emergency Response Simulator is not included with this bridge. Install and validate the required Nights Software resource separately.
What this resource connects
ers_integration connects several resources that you install separately. It does not replace ERS, your framework, dispatch, interaction system, radial menu, or database.
- Framework API
- qb-core; Qbox only through compatible QB exposure
- Dispatch
- PS Dispatch with manual alert additions
- Database
- oxmysql plus INSTALL ME/SQL/ers_database.sql
- Simulator
- night_ers installed and validated separately
QBCore API boundary
The manifest and runtime code call qb-core directly for player, job, money, and framework behavior. A Qbox server needs a tested compatibility resource exposed under the qb-core name and API surface.
Dispatch and location boundary
PS Dispatch receives the manually added alert definitions while nearest-postal supplies location context. Validate the installed PS Dispatch version before merging repository snippets.
Interaction boundary
The selected target and radial-menu resources expose duty, service, database, and common ERS actions. Job and duty restrictions must be tested in the actual menu and target versions in use.
MDT and service records
Validate the complete record set
Test profiles, vehicles, calls, reports, personnel, services, dispatch, and callout history against the imported schema. Treat any table or query error as an incomplete installation rather than an ERS callout failure.
Keep reward handling conservative
Arrival and traffic-stop bonuses are optional and are marked as potentially exploitable in the repository. Disable them or validate their complete server path before enabling them on an economy server.
Known limitations
Qbox is not a native framework mode
There is no independent Qbox selector in the current integration. Compatibility depends on a bridge that behaves like qb-core for the APIs this resource calls.
Denied service requests can still announce arrival
The repository documents a known case where an arrival notification may appear even after a service request is denied. Confirm the actual request outcome before relying on that notification.
Pursuit-backup exports remain work in progress
Five pursuit-backup exports exist in source but are explicitly labeled WIP. They are not documented here as a stable public API contract.
Updating
Merge integration files instead of replacing them blindly
Back up the active PS Dispatch, radial-menu, config, and database files, compare repository changes, and reapply local jobs, permissions, rewards, and alerts deliberately.
Revalidate every external boundary
After an update, repeat duty, traffic stop, callout, pursuit, service request, dispatch, target, radial, reward, and MDT persistence tests because each path crosses independently versioned resources.
Troubleshooting
Dispatch alerts are absent
Confirm PS Dispatch is running, the supplied alert additions were applied to the correct version, and the configured event names were not changed.
Radial or target actions are missing
Confirm the configured qb or qbx radial resource and supported target system start before the integration, then review job and duty restrictions.
MDT data does not persist
Confirm the included SQL was imported, oxmysql is started, and the server console reports no schema or query errors.
A callout does not reach the framework
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.
Reference
Crosshair command
Toggle the integration's crosshair utility for the current player.
/togglecrosshairDatabase installer
The current schema installer is stored at INSTALL ME/SQL/ers_database.sql. Import it through the server's normal database administration workflow before testing MDT features.
- This is a source-available, non-commercial integration rather than an open-source release.
- The QBX radial-menu examples should be reviewed against the installed menu version before copying them.
- Do not describe this as drag-and-drop: PS Dispatch and radial-menu edits are required.
- The repository notes that an arrival dispatch event may appear even when a service request is denied.
- Emergency Response Simulator, PS Dispatch, and other integrated resources retain their own licenses and support channels.