Integrations

Scripts you control should call the exports directly. To restyle notifications from a framework or third-party script, redirect the framework’s central notification function.

These edits are inside another resource and may be overwritten by an update. Keep a copy and compare the function signature before reapplying it.

Keep ensure elvisuals_notify before resources that use its exports.

ox_lib

Open ox_lib/resource/interface/client/notify.lua. Add this guard immediately after function lib.notify(data) and leave the rest of the function unchanged:


if GetResourceState('elvisuals_notify') == 'started' then
    return exports['elvisuals_notify']:notify(data)
end

The early return sends ox_lib notifications to El Visuals. If elvisuals_notify is stopped, ox_lib continues through its original renderer.

Leave this disabled:


Config.CaptureOxLib = false

ox_lib fields without an El Visuals equivalent, such as icon animation, icon color, inline styles, and custom sound tables, are not carried across.

QBCore

Open qb-core/client/functions.lua, find QBCore.Functions.Notify, and replace that function with:


function QBCore.Functions.Notify(text, texttype, length, icon)
    if type(text) == 'table' then
        local caption = text.caption and ('**%s**\n'):format(text.caption) or ''
        text = caption .. tostring(text.text or '')
    end
 
    return exports['elvisuals_notify']:legacy(text, texttype, length)
end

The four-argument signature matches current QBCore. The legacy export maps QBCore types such as primary, police, and ambulance to info. QBCore’s optional icon is not forwarded.

Leave this disabled when the function is redirected:


Config.CaptureFramework = false

QBCore’s QBCore:Notify event calls QBCore.Functions.Notify, so the replacement also covers notifications sent from the server through that event.

ESX

Open es_extended/client/functions.lua, find ESX.ShowNotification, and replace it with:


function ESX.ShowNotification(message, notifyType, length, title, position)
    return exports['elvisuals_notify']:notify({
        type = notifyType,
        title = title,
        description = message,
        duration = length,
    })
end

ESX registers esx:showNotification with this function, so server-sent notifications use the same redirect. El Visuals placement comes from Config.Anchor; the ESX per-call position value is not used.

Leave this disabled when the function is redirected:


Config.CaptureFramework = false

About the capture settings

Config.CaptureOxLib and Config.CaptureFramework listen for public notification events. They do not turn off the framework’s own renderer, so enabling them on an otherwise unchanged framework can draw two notifications.

Use the redirects above for complete, single-renderer behavior. Use a capture setting only when you have separately disabled the original renderer and know the scripts involved send the matching event. Capture settings cannot intercept direct function calls across resource boundaries.

After a framework update

If notifications switch back to the framework style, check whether the edited file was replaced. Reapply the small redirect against the new function rather than replacing the entire updated file.