Installation and First Notification

Download and install

1. Download Murphy Notify from its Workshop page.
2. Extract the complete archive into your server's resources folder.
3. Name the resource folder murphy_notify, with fxmanifest.lua directly inside it.
4. Keep dataview.lua and client.lua. The manifest must load the data-view helper first.
5. Add the resource before scripts that use its notifications:

ensure murphy_notify
# Start your dependent resources below this line.

This guide covers the client.lua implementation with ShowTooltip and murphy_notify:Tip. It has no declared manifest version. No SQL import is needed for this notification library.

Show your first notification

If you are installing a dependency, trigger a normal action in the dependent script. If you are integrating Notify into your own resource, call it from a client Lua file:

exports.murphy_notify:ShowTooltip("Your changes have been saved.", 3000)

3000 means three seconds. The equivalent client event is:

TriggerEvent("murphy_notify:Tip", "Your changes have been saved.", 3000)

From server code, send the event to the intended player. In this example, playerId is the connected player's server ID selected by your existing server logic:

TriggerClientEvent("murphy_notify:Tip", playerId, "Your changes have been saved.", 3000)

Common client exports

Export names are case-sensitive. Event names are separate: murphy_notify:Tip calls ShowTooltip, while murphy_notify:NotifyTop calls ShowLocationNotification.

Notifications with an icon

Use a texture dictionary and icon that exist in the game. The NotifyLeft event loads the requested dictionary and falls back to a generic tick if the dictionary is unavailable:

TriggerEvent("murphy_notify:NotifyLeft",
    "Delivery", "Your parcel is ready.",
    "generic_textures", "tick", 4000
)

Direct advanced exports expect the caller to prepare the texture dictionary. Start with the event example when testing an icon.

Updating

Keep a copy of any local edits, replace the complete resource and restart it in a maintenance session. Test one plain message and one icon notification from the scripts that use it.