Config.Notify option that lets you choose the system already running on your server. Most scripts also include a separate notify.lua file that you can edit freely to wire in any custom solution.
Choosing a Notification System
SetConfig.Notify in config.lua to the identifier that matches your preferred system:
config.lua
Some scripts use a different key name for their notification setting — for example
Config.NotifySystem instead of Config.Notify. Always check the inline comments in the script’s own config.lua for the exact key name and accepted values.sh-notify: The Recommended Option
sh-notify is SH Development’s own lightweight notification resource and the default across the entire catalogue. It is free to use, requires no additional dependencies, and integrates seamlessly with every other SH Development script.Calling sh-notify from Your Own Scripts
You can use sh-notify in your own resources by calling its export directly on the client side:Examples
Parameter Reference
Using a Custom Notification System
If your server already uses a notification resource not listed above — such as GTA-style scaleform notifications, a custom NUI panel, or a proprietary system — setConfig.Notify = 'custom' and then edit the notify.lua file found in the resource folder.
notify.lua is escrow-ignored, meaning it is always fully editable regardless of the script’s protection level. Replace the body of the Notify function with a call to your own system:
notify.lua
Notification System Comparison
sh-notify
Best choice for most servers. Zero extra dependencies, consistent styling, and built-in support across all SH Development scripts.
okokNotify
A popular community notification library. Set
Config.Notify = 'okok' and ensure okokNotify is running — no further changes needed.Custom
Full control. Edit
notify.lua to call any export, trigger any event, or display any UI element your server supports.