With FxEvents you can send and get values between client and server using an advanced event handling process.
Signatures are encrypted per each client and using the proviced MsgPack binary serialization you can hide contents from malicious clients!
To work you only need to add FXEvents.Client.dll
or FXEvents.Server.dll
and Newtonsoft.Json.dll
(In case of json serialization) to your resource.
No need of any external library for MsgPack, the event system uses the internal MsgPack dll provided with fivem itself!!
Usage examples:
public class Main : BaseScript
{
public Main()
{
// The Event Dispatcher can now be initialized with your own inbound, outbound, and signatures.
// This allows you to use FxEvents in more than one resource on the server without having signature collisions.
EventDispatcher.Initalize("inbound", "outbound", "signature");
}
}
EventDispatcher.Mount("eventName", new Action<ISource, type1, type2>(([FromSource] source, val1, val2) =>
{
// code to be used inside the event.
// ISource is the optional insider class that handles clients triggering the event.. is like the "[FromSource] Player player" parameter but can be derived and handled as you want!!
// Clientside is the same thing without the ClientId parameter
}));
The library only works in client <--> server communication.. for the moment same side events are not working but the feature will be added in the future!
// clientside
EventDispatcher.Send("eventName", params);
// serverside
EventDispatcher.Send(Player, "eventName", params);
EventDispatcher.Send(List<Player>, "eventName", params);
EventDispatcher.Send(ISource, "eventName", params);
EventDispatcher.Send(List<ISource>, "eventName", params);
EventDispatcher.Mount("eventName", new Func<ISource, type1, type2, Task<returnType>>(async ([FromSource] source, val1, val2) =>
{
// code to be used inside the event.
// ISource is the optional insider class that handles clients triggering the event.. is like the "[FromSource] Player player" parameter but can be derived and handled as you want!!
// Clientside is the same thing without the ISource parameter
return val3
}));
// clientside
type param = await EventDispatcher.Get<type>("eventName", params);
// serverside
type param = await EventDispatcher.Get<type>(ClientId, "eventName", params);
type param = await EventDispatcher.Get<type>(Player, "eventName", params);
Callbacks can be called serverside too because it might happen that the server needs info from certain clients and this will help you doing it.
The library comes with some goodies to help with customization and debugging serialization printing.
string text = param.ToJson();
type value = jsonText.FromJson<type>();
byte[] bytes = param.ToBytes();
type value = bytes.FromBytes<type>();
byte[] bytes = param.ToBytes();
string txt = bytes.BytesToString();
byte[] bytes = txt.StringToBytes();
type value = bytes.FromBytes<type>();