feat(scripting/net): Unreliable network events

[tens0rfl0w]

Goal of this PR

There are certain scenarios where resource developers may want to send frequent data that is not state-critical (i.e., can be lost). Currently, all script-transmitted data is treated as reliable (ACK, resends, etc.), which can introduce a noticeable hit on general server performance when used for data that should not get sent as reliable.

How is this PR achieving the goal

• Introducing a new API to send unreliable client and server network events
• All new API functions are equal to the existing reliable send functions:
  • Lua: TriggerUnreliableClientEvent and TriggerUnreliableServerEvent
  • JS; emitUnreliableNet, TriggerUnreliableClientEvent and TriggerUnreliableServerEvent
  • C# V1: Player.TriggerUnreliableEvent, TriggerUnreliableClientEvent and TriggerUnreliableServerEvent
  • C# V2: Player.TriggerUnreliableEvent, Events.TriggerUnreliableAllClientsEvent, Events.TriggerUnreliableClientEvent, and Events.TriggerUnreliableServerEvent

Implementation has been tested on all available ScRTs and should not introduce any breaking changes (*__INTERNAL natives are already declared as internal functions).

This PR applies to the following area(s)

FiveM, Server, Natives, ScRT: Lua, ScRT: C#, ScRT: JS

Successfully tested on

Game builds: Not applicable

Platforms: Windows, Linux

Checklist

• Code compiles and has been tested successfully.
• Code explains itself well and/or is documented.
• My commit message explains what the changes do and what they are for.
• No extra compilation warnings are added by these changes.

Fixes issues

/

[manzarek123]

This is going to break a lot of server since people are using TRIGGER_CLIENT_EVENT_INTERNAL directly

Maybe last arg should be "unreliable" instead of "reliable"

https://github.com/overextended/ox_lib/blob/a2a711498658d36e51bd9853f681cacac502f9bb/imports/triggerClientEvent/server.lua#L14

[tens0rfl0w]

This is going to break a lot of server since people are using TRIGGER_CLIENT_EVENT_INTERNAL directly

Thanks for pointing this out!

I went with moving the shared code paths for reliable and unreliable network events one step deeper internally, so this shouldn't break any usage of backing natives anymore.

(ScRTs now invoke TRIGGER_UNRELIABLE_*_EVENT_INTERNAL)