Module 04 · Bonus

Latent events: TriggerLatentServerEvent & TriggerLatentClientEvent

A regular TriggerServerEvent hands the whole payload to the network layer in one shot. For small messages that is fine. For big tables, image buffers, or character export blobs, that single burst can stall a player's connection long enough to time them out. Latent events stream the same payload at a controlled rate, in bytes per second, so the connection keeps breathing while the data trickles across.

You'll learn: When to swap TriggerServerEvent for TriggerLatentServerEvent, what the bps parameter actually does, how to size it, and why broadcasting latent events to all players is a trap
Time: ~14 minutes
Prereqs: Lesson 14 (TriggerServerEvent / TriggerClientEvent)
Outcome: You know the rule of thumb (small = regular, big = latent), you can size bps for any payload, and you can send latent events in both directions safely

BEFORE YOU START

Build it

Make the resource folder

The server has one folder for this lesson.

Inside your server's resources folder, create this folder:

code

resources/qu_latent_events

Latent events: TriggerLatentServerEvent & TriggerLatentClientEvent

Build it

Make the resource folder

Create the files

Write fxmanifest.lua

Write the lesson code

Start and test it

Keep reading the full lesson