Scripts/LRS Notifications
AVAILABLE NOW · V1.1.0

LRS Notifications

A premium standalone FiveM notification system with configurable themes, layouts, animations, positions, persistent alerts, transactions, player preferences, admin styling tools and framework-aware audience routing.

Available nowFiveMStandalone coreQBCore / Qbox / ESX routing
Official FiveM release$9.99Asset Escrow ProtectedLoading community rating…Open official storeTebex checkout · Cfx.re entitlement
LRS Notifications product artwork showing police, success, transaction, warning, server, info, EMS and reward notification styles around the LRSCRIPTS logo
LRS NotificationsVersion 1.1.0 · Official product artwork

Overview

LRS Notifications gives server owners one polished notification layer instead of a collection of mismatched alerts. The core works standalone, while optional compatibility listeners and server routing can connect into common FiveM frameworks when enabled. Presentation can be controlled globally or per notification without hard-coding every alert into the interface.

Included in v1.1.0

9 notification presetsSuccess, error, warning, info, police, EMS, mechanic, money and server presentation presets.
5 notification modesStandard, announcement, emergency, transaction and persistent notification behavior.
5 themes · 3 layouts · 4 animationsSignature, glass, solid, minimal and neon themes with standard, compact and capsule layouts plus slide, fade, bounce and zoom animations.
6 independent positionsTop-left, top-center, top-right, bottom-left, bottom-center and bottom-right positioning with independent visible stacks.
Persistent & transaction alertsID-based persistent notifications, dismissal/update support and dedicated transaction amount display.
Duplicate grouping & audio controlRapid matching alerts can group into one visible card while duplicate audio is separately throttled.
Player preferencesServer-controlled settings can let players save position, sound volume, UI scale, animation, theme and layout preferences locally.
LRS Style StudioACE-protected admin styling interface with live local preview and Lua presentation-value output for configuration or integrations.
Audience routingServer exports can target all players, jobs, gangs, nearby players or ACE groups with QBCore, Qbox and ESX-aware routing.
Standalone notification APIClient exports/events and server exports remain available without requiring a framework for normal notifications.

Requirements & compatibility

Normal notification use is standalone and does not require a framework. Optional routing can auto-detect QBCore, Qbox or ESX. Optional QBCore and ESX notification-event compatibility listeners are disabled by default to avoid duplicate interfaces and should only be enabled when intentionally replacing an existing notification path.

PlatformFiveM
Core frameworkNone required
RoutingStandalone / QBCore / Qbox / ESX
External CDNNone
Audio filesNone required

Installation

Place lrs_notify in your resources folder, review config.lua, add ensure lrs_notify to server.cfg, then restart the resource or server. Integration examples are included with the resource.

ensure lrs_notify

Open Notifications Docs

Build notes · v1.1.0

Version 1.1.0 is the current public release. The release expands the standalone notification core with persistent player preferences, the in-game settings interface, the ACE-protected LRS Style Studio, framework-aware audience routing, optional framework notification compatibility, resolution-aware scaling and reduced-motion support. The release package also includes LRSCRIPTS commercial licensing/notice files and selective Cfx.re Asset Escrow configuration while keeping intended configuration and integration examples editable.

Release stateProduction release 1.1.0.
DeliveryOfficial LRSCRIPTS Tebex / Cfx.re FiveM asset entitlement.
Editable filesConfiguration and integration examples remain available for server-specific setup.
Protected implementationCommercial release uses selective Cfx.re Asset Escrow for protected Lua implementation.

Global Changelog

Support

For the fastest diagnosis, include LRS Notifications version 1.1.0, your framework if routing is enabled, the exact integration call or event being used, and the first relevant server-console or client F8 error.

Support Guide