Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TriggerLatentServerEvent doesn't work anymore on latest fivem artifacts #3041

Open
0x0f234 opened this issue Dec 25, 2024 · 1 comment
Open
Labels
bug ScRT: Lua Issues/PRs related to the Lua scripting runtime triage Needs a preliminary assessment to determine the urgency and required action

Comments

@0x0f234
Copy link

0x0f234 commented Dec 25, 2024

What happened?

After the latest FiveM update, the TriggerLatentServerEvent function has ceased to function. This issue is preventing the reliable transfer of large data payloads between client and server, a critical feature for many resources. The server is not receiving any data or triggering the event at all.

Expected result

The server should receive the event and process the payload as it did in previous builds.

Reproduction steps

  1. Update FiveM to the latest build.
  2. Implement or use a script that calls TriggerLatentServerEvent to send a payload from a client to the server.
  3. Observe that the event does not trigger or process as expected on the server side.

Importancy

Unknown

Area(s)

FiveM, FXServer, ScRT: Lua

Specific version(s)

FXServer 12160

Additional information

No response

@0x0f234 0x0f234 added bug triage Needs a preliminary assessment to determine the urgency and required action labels Dec 25, 2024
@github-actions github-actions bot added the ScRT: Lua Issues/PRs related to the Lua scripting runtime label Dec 25, 2024
@Szpachlan
Copy link

there is an issue with TriggerLatentClientEvent too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug ScRT: Lua Issues/PRs related to the Lua scripting runtime triage Needs a preliminary assessment to determine the urgency and required action
Projects
None yet
Development

No branches or pull requests

2 participants