Latent events not working after using longer name than other events

FiveM Discussion Bug Reports
1

If you trigger a Latent Event (TriggerLatentClientEvent) the event name doesn’t get cleared automatically, this causes there to be leftover data if you trigger later events.
The array in question seems to be the one in “citizen-resources-core/EventReassemblyComponent.cpp” on line 291, but can’t say for sure, don’t really have hands-on experience with C++.

Code to replicate would be something along the lines of this:

TriggerLatentClientEvent("TestEventNameWhichIsLongToFillTheBufferWithAnnoyingData", -1, 0, 'Some Random Data')
TriggerLatentClientEvent("ShortEventName", -1, 0, 'Some Random Data')

This would cause the eventName (in netEventLog) of the second event to be: “ShortEventNamehichIsLongToFillTheBufferWithAnnoyingData”

3

Had a deeper look into it, seems it’s missing a null-termination on the end of the string.
Don’t really know why this does appear on the LatentEvents and not on the normal events though since they seem to be handled in almost the same way.

Edit:

Alright figured the difference between the two out, the normal events do event name length +1 to get a null terminated string, latent events don’t do this, I’ll get a test build going tomorrow and I’ll submit a pull request