AWS DEVELOPMENT / DOCUMENTATION

Your server. Our expertise.

Everything you need to install, configure and build.

Installation notes

Use the exact folder, SQL file, dependency and startup order shown for your downloaded package. Some resources contain FXAP-protected runtime files, so their guides cover only the source and configuration that can be inspected.

AWS Notify

A notification and progress HUD resource for FiveM. The included NUI renders notifications and progress messages. config.lua contains framework selection, default display preferences, language, duration limits, and inventory-notification filtering.

Requirements and install

The manifest declares no framework, inventory, or database dependency. Framework integrations are optional and depend on the configured bridge/resources. The manifest references FiniAC; keep it available or remove its entry if you do not use that integration.

Keep the folder name rio-notify, then add:

ensure rio-notify

There is no SQL file. Set Config.Framework to auto or your supported framework. Review Config.DefaultConfig and the inventory toast patterns for your server's language.

Exports

The manifest exposes Notify, Notif, Progress, StartProgress, IsProgressActive, CancelProgress, and CompleteProgress. The NUI handles notify, clearNotify/clearAll, progress/startProgress, and stopProgress actions.

Example from another client resource:

exports['rio-notify']:Notify('Saved successfully', 'success', 5000)

Use the exact rio-notify resource name. Avoid replacing core notification functions until callbacks have been tested on a development server.

Troubleshooting

Nothing appears: check resource startup, NUI files, and that the export is called client-side.
Duplicate inventory messages: tune SuppressInventoryItemNotifies and its allow/block patterns.
Progress placement is wrong: inspect the NUI stylesheet; not every position option in config.lua controls the NUI layout in this build.

Some client/server Lua files are FXAP-protected. The accessible NUI message handler does not implement the dashboard described by the previous README, so this guide does not claim that feature.