Installation · origen_notify

1. Add to server.cfg

text

ensure origen_notify

origen_notify must start before any resource that calls its exports. Place it early in your server.cfg, after /assetpacks.

2. Framework integration

origen_notify does not auto-hook into any framework. You need to patch the framework resource manually so that its internal notify/drawtext functions delegate to origen_notify.

QBCore

Open qb-core/client/drawtext.lua.

Step 1 — Comment out the existing hideText and drawText functions, then add the following at the top of the file:

lua

local __buffer = {}
 
local function hideText()
    for k, v in pairs(__buffer) do
        exports["origen_notify"]:RemoveHelp(v)
        __buffer[k] = nil
    end
end
 
local function drawText(text, position)
    local key = ""
    local formattedText = text or ""
 
    if string.find(formattedText, "%[.-%]") then
        key, formattedText = string.match(formattedText, "%[(.)%](.+)")
    end
 
    __buffer[text] = exports["origen_notify"]:CreateHelp(key, formattedText or text)
end

Step 2 — Replace the body of QBCore.Functions.Notify with:

lua

exports["origen_notify"]:ShowNotification(message, type, length)

ESX

No official patch is provided at this time. Use the client-side exports directly in your custom resources.

3. No SQL required

origen_notify has no database tables. No SQL to run.