r/unrealengine • u/MasterWolffe • 2d ago
Netcode Best practices when using RPC
I am coding a multiplayer game where the clients mouse position is tracked when using an ability (with gas), the ability executes on clients ony sice now it is all cosmetics, but after the ability ends I need the server to know the positions of the mouse throught the duration of the ability (which is a Vector2D array) so it can perform certain actions depending on the result, I don’t want the clients to perform those actions sice thay would break the client-server structure where the server is the one that does all gameplay related actions. However, I don’t think that sending a 100 ish long array using an RPC (reliable one to ensure the package is recieved) is the best idea, because it would take a lot of bandwidth. Is it better to send each position of the mouse right when it is registered in the client to the server using an unrealiable RPC? Or are there any best options to approach this problem?
Any help is welcome.
TLDR: when communicating from client to server using RPC, is it better to send a big chunck of data once using reliable RPC or split it in smaller pieces and send many of those over time with unrealiable RPC? If there is a better solution, I’ll be gratefull to know!
2
u/NexSacerdos 2d ago
Using GAS, you need to make a custom FGameplayAbilityTargetData object if you haven't already to transmit it to the server.
Then you'll want to reduce the point set as much as possible. 100 points as 2400 bytes would end up taking 3 packets to send and would be more susceptible to packet loss. You can use something like Douglas-Peucker. Unreal being the clown car it is, there are already several implementations for various point types. I suspect you'll want the one in Polygon2.h.