Ongoing C++ Gameplay Example Series: Making a Survival Game

[Tom_Looman]

@;410442

Hi there !

As usual thanks for your contribution mate!

Just my 50 cents, I’ve quickly read through parts of the code, and since you like good practices, 's my contribution:

• You’re sending Client messages using FStrings, it makes more sense - in terms of bandwidth, performance - to instead send a uint32, having most of the messages hardcoded on the client. All the client has to do, is open the map of those messages (stored in an XML or w/e), and they get their message. uint32 vs FString… And use that solution for special unpredicted messages, or well, just a combination of both sendClientMessage(uint32 messageID, FString replaceString);

You are totally right mate. I spotted these bumps in networking when I started profiling recently, but wasn’t sending enough yet to warrant priority. IDs are for sure a better way of handling this. If I get this updated in my primary project I’ll see if I can update the survival game too with that.

Thanks!