Add optional networking entity module that synchronizes the entities and the shared data with the clients. This will make it possible to create objects, peds and markers from serverside.
The server will send the entities via a tcp socket or probably websockets and protobuf serialization to the clients. Can't use udp socket because cef doesn't support it. The entities will support serverside and synchronized meta data. The entity types will be generic on serverside and the client will have to decide how to render them when entering / exiting streaming range.
AltV.Net.NetworkingEntity is implemented. Next step is to build another api on top to provide support for serverside objects, markers, checkpoints and peds.
[ ] AltNetworking.CreatePed(uint model, Position position, Rotation rotation, int dimension)
[ ] AltNetworking.CreateObject(uint model, Position position, Rotation rotation, int dimension)
[ ] AltNetworking.CreateBlip(BlipType type, Position position, int dimension)
[ ] AltNetworking.CreateCheckpoint(CheckpointType type, Position position, int dimension)
[ ] AltNetworking.CreateMarker(MarkerType type, Position position, int dimension)
[ ] AltNetworking.CreateTextLabel(string text, Position position, float range, float size, int font, Rgba color, bool entitySeethrough = false, short dimension)
Add optional networking entity module that synchronizes the entities and the shared data with the clients. This will make it possible to create objects, peds and markers from serverside. The server will send the entities via a tcp socket or probably websockets and protobuf serialization to the clients. Can't use udp socket because cef doesn't support it. The entities will support serverside and synchronized meta data. The entity types will be generic on serverside and the client will have to decide how to render them when entering / exiting streaming range.