You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
You can use TriggerLatentClientEvent function to send data to a client that doesn't block the clients network channel. So it would be great if we could register a latent callback instead when needed. This would be more flavourful when sending large amounts of data or for non time critical events, to stop blocking of the client network channel.
Describe the solution you'd like
A function like lib.callback.register call it say lib.callback.registerLatent, which uses TriggerLatentClientEvent instead of TriggerClientEvent for client and TriggerLatentServerEvent instead of TriggerServerEvent for server.
Default of bps of 50000 with an argument to higher or lower it.
Is your feature request related to a problem? Please describe.
You can use
TriggerLatentClientEvent
function to send data to a client that doesn't block the clients network channel. So it would be great if we could register a latent callback instead when needed. This would be more flavourful when sending large amounts of data or for non time critical events, to stop blocking of the client network channel.Describe the solution you'd like
A function like
lib.callback.register
call it saylib.callback.registerLatent
, which usesTriggerLatentClientEvent
instead ofTriggerClientEvent
for client andTriggerLatentServerEvent
instead ofTriggerServerEvent
for server.Default of bps of
50000
with an argument to higher or lower it.Additional context
https://docs.fivem.net/docs/scripting-manual/working-with-events/triggering-events/#triggering-latent-server-events
https://docs.fivem.net/docs/scripting-manual/working-with-events/triggering-events/#triggering-latent-client-events
Hope this makes sense 😊
The text was updated successfully, but these errors were encountered: