Broadcasted Notification System for Roblox

===========================================================

🔔 ROBLOX MODULAR NOTIFICATION SYSTEM

Demo: https://www.roblox.com/share?code=5d6ffc2a6bf04d498787af1f85f8c96a&type=Experien...

===========================================================

Version: 1.0

Author: Jadon Fischer (Fischer Software e.K. / Jadon | Roblox Tutorials)

License: COMMERCIAL USE ONLY (see bottom)

===========================================================

A lightweight and flexible notification framework supporting:

• Client → Client  

• Server → Client  

• Client → Server → Client (optional validation flow)

The system includes modular animations, optional random styling, and multiple

delivery targets — all without requiring controllers or module hierarchies.

-----------------------------------------------------------

✨ FEATURES

-----------------------------------------------------------

🎞 3 Built-in Animations — Move Up, Fade In/Out, Grow/Shrink  

📡 Multi-Target Delivery — One, list, all, all except  

⚡ Direct Bindable Dispatch — Fastest notification method  

🧩 Blueprint-based UI — Simple to style or replace  

🔁 Optional RemoteFunction relay for verified broadcasts  

🎨 Supports random color, animation, and position  

🧱 Clean, readable Lua — No controller structure

-----------------------------------------------------------

⚙️ FILE OVERVIEW

-----------------------------------------------------------

ServerScriptService/

 └─ NotificationServer.lua        -- Handles targeting & distribution

StarterPlayerScripts/

 └─ NotificationClient.lua        -- Handles visual creation & animations

ReplicatedStorage/

 ├─ Remotes/

 │   └─ NotificationAction (RemoteFunction)   -- Client→Server→Client only

 ├─ Bindables/

 │   └─ NotificationAction (BindableFunction) -- Direct client/server dispatch

 └─ Blueprints/

     └─ Notification (GUI template)

-----------------------------------------------------------

📐 SYSTEM ARCHITECTURE

-----------------------------------------------------------

CLIENT (NotificationClient)

---------------------------

• Responds to BOTH:

      notificationActionBF.OnInvoke

      notificationActionRF.OnClientInvoke

• `BindableFunction` is the *normal* notification channel  

• `RemoteFunction` is used ONLY when the client asks the server to forward a message

• `showNotification` builds the GUI and plays:

    – Move Up  

    – Fade In/Out (TextTransparency)

    – Grow/Shrink

• Notifications destroy themselves after completing animation

SERVER (NotificationServer)

---------------------------

The server never creates GUI — it only chooses recipients.

It uses functions:

        sendToPlayer(player, msg, style, color, pos)

        sendToList(list, msg, style, color, pos)

        sendToAll(msg, style, color, pos)

        sendToAllExcept(list, msg, style, color, pos)

Server dispatches notifications using:

        notificationActionBF:Invoke(...)

RemoteFunction is only used when:

• A client requests the server to rebroadcast a notification  

• `ALLOW_CLIENT_BROADCASTS = true`

-----------------------------------------------------------

📡 NOTIFICATION DELIVERY MODES

-----------------------------------------------------------

===========================================================

1️⃣ CLIENT → CLIENT  (BindableFunction, NO ACTION ROUTING)

===========================================================

The simplest, fastest method.  

Client directly calls the BindableFunction, and the same client receives it.

Client call:

    notificationActionBF:Invoke("Hello!", nil, "fade", Color3.new(1,1,1))

Client receives:

    notificationActionBF.OnInvoke = showNotification

✔ No routing  

✔ No “SendToPlayer” action  

✔ No table structures  

✔ Direct arguments → passed directly into showNotification

Use this for:

• Button clicks  

• Local UI feedback  

• Inventory messages  

• Non-server-validated messages

===========================================================

2️⃣ SERVER → CLIENT  (BindableFunction on Server)

===========================================================

The recommended method for most notifications.

Examples:

--- To one player ---

notificationActionBF:Invoke(player, "Quest complete!", nil, "grow")

--- To list of players ---

notificationActionBF:Invoke(playerList, "Dungeon opening!", nil, "fade")

--- To all players ---

notificationActionBF:Invoke(Players:GetPlayers(), "Match starting!", nil, "moveUp")

--- To all except these players ---

notificationActionBF:Invoke({"Player1","Player2"}, "Special event!", nil, "fade")

Server calls automatically forward directly into showNotification on each client.

===========================================================

3️⃣ CLIENT → SERVER → CLIENT (RemoteFunction)

===========================================================

Used when the client wants the server to validate or rebroadcast a message.

Client requests:

    notificationActionRF:InvokeServer("SendToAll", "Hello everyone!", "fade")

Server receives the request in:

    notificationActionRF.OnServerInvoke

Server then uses normal dispatch:

    sendToAll(...)

This flow is ONLY allowed when:

    ALLOW_CLIENT_BROADCASTS = true

-----------------------------------------------------------

🎞 ANIMATION STYLES

-----------------------------------------------------------

MOVE UP  

--------

Slides upward 10% of the screen.

FADE  

--------

Text transitions:

    1 → 0 → hold → 1

GROW  

--------

Label size transitions:

    0 → original → 0  

Best for big impact notifications.

-----------------------------------------------------------

🧪 CLIENT USAGE EXAMPLES

-----------------------------------------------------------

Direct local message:

    showNotification("Saved!", nil, "fade")

Client → Client via BindableFunction:

    notificationActionBF:Invoke("Inventory updated!", nil, "grow")

Client → Server → Client:

    notificationActionRF:InvokeServer("SendToAll", "Hi everyone!", "fade")

Demo panel (UI buttons):

— For demonstration only  

— Not required for the system to work

-----------------------------------------------------------

🖥 SERVER USAGE EXAMPLES (BINDABLE FUNCTION — RECOMMENDED)

-----------------------------------------------------------

--- To one ---

sendToPlayer(player, "Your crops are ready!", "grow")

--- To list ---

sendToList({p1, p2}, "Team Bonus Active!", "fade")

--- To all ---

sendToAll("Server shutdown in 2 minutes!", "moveUp")

--- To all except ---

sendToAllExcept({p1}, "Everyone but p1 sees this.")

-----------------------------------------------------------

💡 TIPS

-----------------------------------------------------------

• Client→client always bypasses actions  

• Use BindableFunction for 99% of cases  

• Use RemoteFunction ONLY when client should ask server permission  

• Your notification blueprint defines the look — code never touches layout  

• Demo panel is optional & not part of core system  

-----------------------------------------------------------

⚖️ LICENSE — COMMERCIAL USE ONLY

-----------------------------------------------------------

Copyright (c) 2025

Jadon Fischer (Fischer Software e.K. / Jadon | Roblox Tutorials)

Permission is granted to the purchaser to modify and use in commercial Roblox

experiences. Redistribution in any form is prohibited.

-----------------------------------------------------------

✅ CREDITS

-----------------------------------------------------------

Developed by Jadon Fischer (Fischer Software e.K. / Jadon | Roblox Tutorials)

Version 1.0 — clean, controller-free, high-performance notifications.

===========================================================