Protocol for game networking?

[L B]

Title says it all.

I'm guessing UDP, with an initialization packet, but that doesn't seem too reliable.

I'd work with TCP, but I get duplicated data in C#, since the only according SocketType is Stream, which duplicates data.

 

Ideas?

[L B]

Kept thinking, UDP is definitely the way to go. However, I'm used to a Multithreaded TCP Server approach, with each thread a socket. My question is: Do I actually only need 1 UDP socket for all my connections? If so, I must provide some kind of identification system in my sent packets.

 

This seems very troublesome. I would love to use TCP, but I get some kind of annoying duplication in C#. I'm not even sure if this is normal or not, but I do know I used to work with the same C# server architecture with a client that I didn't make that used TCP, and there was no duplication.

[Rick]

Use reliable connected UDP (it's a layer over UDP that makes it reliable and handles keeping it connected for you and still faster than TCP). RakNet has this already built in and I've used it and love it.

[Josh]

Enet has a "reliable" flag for packets. It's not 100% reliable, but it seems to work pretty well. If a packet is missed, the program just resends it.

[L B]

I'll use TCP actually. My game is not a shooter, so it's not fast paced enough to justify UDP. Thanks for the advices.

[Ending Credits]

Since we have this thread already, when is the networking documentation going to get updated?

 

There's no information at all on the TEvent type.