Common Questions

Nothing appears after installation

Notify waits for another resource to request a message. There is no universal notification menu or player command to open. Trigger an action in a script that uses Notify, or run the client example in Installation.

No such export, or an error mentioning DataView

Check the folder name, resource start order and exact export capitalization. Keep the complete archive: dataview.lua must load before client.lua. Call client exports from client code; from the server, use the corresponding client event with a player ID.

The notification has no icon

First test the documented generic_textures / tick pair through murphy_notify:NotifyLeft. If that works, check your custom dictionary and icon name. A dictionary may exist while the requested icon inside it does not. Direct advanced exports do not perform the same dictionary-loading step as the wrapper events.

Messages disappear too quickly

Durations are numeric milliseconds. Use 5000 for five seconds, not 5. Keep messages short enough to read within the chosen duration.

Text is in the wrong language

Notify displays the text supplied by the calling resource. Change the message in that resource's translations or configuration. Changing Notify alone cannot translate every caller's messages.

Can I replace all framework notifications with this?

Only scripts integrated with Notify will use it. Replacing another notification system requires adapting the calling code and its arguments; renaming a folder does not make their APIs interchangeable.

What should I include in a support ticket?

Send the calling resource's name, the exact export or event, its arguments, whether it runs on the client or server, and the first relevant F8/server error. Mention whether the basic tooltip example works.