JM-Pimping supports four notification backends. Switch between them by editing a single line in config.lua.
Quick Setup#
- Open
config.lua. - Find the
Config.Notificationssection. - Set
systemto your preferred option (see table below). - Run
restart JM-Pimpingin the server console.
Available Systems#
| Value | Requirement | Notes |
|---|---|---|
"qb-core" | QBCore framework | Default. Works out of the box on any QBCore server. |
"qb-phone" | qb-phone resource | Phone-style notifications with a heart icon. |
"ox_lib" | ox_lib resource | Modern UI with customisable on-screen position. |
"chat" | None | Coloured chat messages — works with any framework. |
QB-Core (Default)#
Config.Notifications = { system = "qb-core", duration = 5000, position = "top-right"}QB-Phone#
Config.Notifications = { system = "qb-phone", duration = 5000, position = "top-right"}Requires qb-phone to be running. Uncomment the qb-phone dependency line in fxmanifest.lua.
OX Lib#
Config.Notifications = { system = "ox_lib", duration = 5000, position = "top-right"}Requires ox_lib to be running. Uncomment the ox_lib dependency line in fxmanifest.lua.
Position options for ox_lib: top, top-right, top-left, bottom, bottom-right, bottom-left, center-right, center-left.
Chat Messages#
Config.Notifications = { system = "chat", duration = 5000, position = "top-right"}No extra resources required. Messages appear in the chat box with a [JM-Pimping] prefix and colour-coded by type.
Testing Notifications#
Run the following command in-game to preview all four systems at once:
/testnotifsThis fires a sample notification through every available backend so you can confirm which systems are active before committing to one.
If you specify an invalid system name the script automatically falls back to qb-core notifications.