Incredibly underrated video. Fantastic production!

I’ve taken networking courses in college and can say with certainty that if the instructors presented the topics like you have here, much more of the class would be engaged with the intricate web *pun intended* of subject matter!

2:04 I like how he avoided making a demonic sign whenhe was example peer to peer 😂

Damn, I am so interested in a Unity multiayer tutorial by you. Explaining and comparing the different methods on how to implement multiplayer.

another thing worth noting is that any way you allow the client to be authoritative, you will open space for hacks more easily, since it is just modifying the game to modify the behavior. i have seen some games (like Rocket League) use prediction on the client for the player's own movement so the server still has full control of the player's position without implying fluidity. this should be more difficult to implement, but is way more secure btw, nice video ;)

This is such an insanely good high level overview. As someone who codes very very little I felt like I was able to follow everything you were talking about and really love that I now have a better understanding of how this works. Thank you!

This is a really beautiful video, it helped a lot understanding things I had never actually understood before. Thank you so much, keep up the amazing content!

Interesting and simple, I love it. Keep up a good work! Subscribed

That's how to present a complex topic in a short precise manner - very well done.

Really well put together, great job on the explanation

Thank you for creating and sharing this video!

Hey bro i just wanted to say this video was actually extremely interesting. Good shit i’ll be looking out for other uploads from you

Very comprehensive video. Nerds are the MVPS!

Scratch online multiplayer games are usually done using peer to peer connection. Tit is possible to make the host type, but is harder. The hardest obe to make on scratch, is the client server, because you have to have a special case in the project to make it run as a server or a client, and also leave the project running forever, and not have to worry about being disconnected. The best way to do that, would be to use an external server that communicates with scratch's server, which is against their tos, so it is rare to find a project that uses that.

3 years of my experience of trial and error, sweat and tears, in just 15 minutes video.. Where were you all this time? Well done explaining everything, I wish I saw this 3 years ago

Amazing video, thank you for sharing your knowledge

Wowww! Incredibly underrated, thank you for this useful info :)) 😊

This was an excellent overview. 🤔👍

Woow nice production and content

Damn this helped me understand more about Computer networks than the entire semester of my college life..........thank you so much :)

Explained very clearly. Loved it. Great work 👍

I really related to the joy of making multiplayer games! I definitely want to make one again in the future

Fantastic video!

Amazing explanation of how multiplayer code works bro. I used to do development in Unity back in 2009-2012, and never even touched netcode for some reason lol

wow, this presentation ist amazing

Amazing Video thank you!

Awesome video! I would love a follow on video about state prediction, reckoning and rollback

fantastic overview

Great video.

Amazing video! thank you! I’m trying to make a peer-hosted setup for my game

thank you for this video, it makes me relly want to make my own games.👍

Very well explained, thumbs up for sure.

I have no idea how to make a game but for the most part, I was actually able to keep up with the content a little bit.

This video is more informative than the wikipedia page on multiplayer technologies for games

Great Video!

This is an amazing video!

Awesome video (Y)

This is a really great and informative video!

An important clarification to make: an IP address refers to a device on a network, the address tells the sender whether the receiving device is on the same LAN or not, as well as where to send to. Ports refer to an application on a device, for example, a port number can tell the device whether the signal it receives is meant for a web browser or a game. A socket pair refers to both an IP address and the port number, meaning you can know which program is being talked with on which device.

Well done!

Well-Done

Very good!

Nice video. Very informative :) TCP stands for Transmission Control Protocol.

I was just watching this video for entertainment mostly, but actually learned that I should use unreliable messages in the networked game I was working on

Really thank you for making this video.

Superb overview, thanks Nick 👍

4:52 It is a bit problematic to say that an IP address points to an entire network and a port points to a particular computer, as this is only true in the context of network address translation (from the perspective of a server or peer). In the general case, an IP address refers to a network interface and a port is associated with a particular application on a computer. Just thought it's worth pointing out.

I'm a self-taught junior web developer and a gamer. Once I learnt web sockets, RPC and etc couple days ago, I wondered how multiplayer games work. Your video helped me to understand it, and made me more curious about it so I'll deep dive in it. thank you so much ❤

I wish videos like these went deeper. For example, often the client/server, host, and peer to peer multiplayer models are presented as if a game dev team chooses one and is done; however, multiplayer games like Destiny and others mix and match multiplayer models depending on how sensitive an operation could be versus how much it would cost to maintain the infrastructure. Another example: what about "multiplayer services" aka APIs (often REST) that facilitate stuff like matchmaking or choosing a server; you can think of these as "the things that don't need a game server instance running a game simulation to accomplish" like a server browser or quick play.

As a solo dev is #1 rule to avoid making multiplayer :) But this video is great to show friends that try to convince me otherwise, so they understand why not!

awesome

you forgot how udp packets are not guaranteed to be delivered at all! (reliability is one of the main points of tcp)

Sad there's only 100k views. It deserves several million

This works for absolute beginners but have to say after studying the topic a lot I see some misguiding information. Overwatch for example definitely does not client authoritative model. They do a lot of checks on the server side and will rollback a client that goes out of state - showing it's not client authoritative system. They just like to prefer clients in a lot of their checks on the server side but the authority is saved for the server and the server does a bunch of checks to make sure clients behave. Also you don't need to use client authoritative model to fix the problem where your actions take a lot of time as they are verified by the server. You just need to execute the actions on the client as you send them to server BUT revert them back if prediction does not match reality (that's what Overwatch does too!). Favor the shooter != client authoritative. Authority in networking means basically who has "final say". Clients in Overwatch don't have final say. Also many libraries exist that combine UDP into TCP like system while still being faster than TCP, with still some TCP benefits. Also one thing to note is that it's very common place to use combination of client hosted & dedicated server for a same game. They both use Client-server model.

So you're telling me that rollback has been basically industry standard for decades, but the fgc is just recently making the transition? My guess for why they took so long is that fgs are incredibly dependent on frame data and exactly how many frames it takes for an attack to happen (and block/hit stun duration, recovery frames etc.), so the idea of allowing a slight desync, even if it's quickly corrected, may have been a hard sell. Instead, for years fg netcode has been entirely delay based, adding a frame buffer to your inputs based on the connection quality so you and your opponent are (in theory) always synced. The issue here is that the connection has to be good and if it's not, more delay would be added to compensate. The max most would tolerate is 3-4 frames of delay, much more than that and inputs feel awful. The FGC's version of the standard outlined very well in this video, what we call rollback, still has a frame delay, but it's much lower than in purely delay based netcode and because it uses the prediction method described in the video, it can let your input go through on your client instantly. Basically it moves the buffer behind the scenes like most other competitive games instead of just kinda being how you play the game. I'm sure the FGC's various versions of rollback have their own methods of dealing with a desync and that there are plenty of reasons fgs took so long to use this tech, but what you outlined in the video is essentially how it works. Rollback was sold to the FGC as this revolutionary new way of handling netcode, but it seems they just took what already existed and adapted it to fgs. Still impressive that i can play Guilty Gear with someone on the opposite side of the planet with little to no lag, so I'm not complaining about the implementation. It's just frustrating as someone who loves the genre to know that the tech hailed as the savior of online fg play (and, as of covid, the savior of the FGC, at least during lockdown) has existed for probably my entire life

Have a great day too! :)

This is my computer science revision

Please make tutorials I love the format of this video. The thing with multiplayer that makes it so hard for me is the lack of good resources

4:56 that’s not quite right. A port specifies which program on an operating system (i.e. host) gets to receive an incoming packet. For example port 80 is usually dedicated to an http server while 22 is for ssh. In both cases, the same IP can be used and the port is only so the receiving computer knows which packet to forward to which program.

3:35 TCP is transmission control protocol

my hopes for making a multiplayer fps have truly been smashed

Where was this video during my previous year in school?

If we're using UDP for fast transfer for online games, cant we develop a game that is run on a developer owned server client that sends a stream of the game audio+video to the players and receives controller input from the players? In order to avoid any conflicts or sync issues.

I have experienced that exact thing of getting hooked by roadhog when I was behind a corner and even tho I knew why it happened it's still incredibly frustrating :

How does valve cs2 sub ticks work?

4:50 This is factually incorrect, in the standard TCP/UDP protocol ip is the address of a host, while port is the address of a process on that host.

I never knew this one salient point before, but apparently clients are color blind. They'll predict game state in green, but call it red. :P

small correction TCP stands for transmission control protocol, not transmission communication protocol

pretty sure you messed up some of the networking info. ports are not limited to a single pc, they're limited to one IP, so you cannot have multiple applications listening to the same port on the same ip (mostly, on windows at least), but you can have multiple applications running on different IPs with the same port number :]

in my years of using unity i've used serialization countless times, but somehow i didn't really understand what it was until i watched this...

Really interesting! I was slightly disappointed though that this video seems to only explain online multiplayer, while the thumbnail shows a distinctly local multiplayer setting (which is what I was looking for). Maybe change the thumbnail?

weird this game I play is called Let It Die and it has a weird Offline-Online Model, in terms of exploiting the game there is nothing stopping you but the second you have your health past max and use an npc or action that gets sent to the server, it kicks you off and it's a temporary kick in that moment or a ban after 7 days, there is also data grabbed from everyone's waiting room as a Clash of Clans type base raiding feature exist, where the other people have to be offline or away from their base. there is no true online multiplayer experience, just an off "I'll raid you base and I can die with my weapon out and drop it for you when you get back online"

Does anyone know whether QUIC made its way into any of these? 🤔

Cute bun!

10:43 Is this the basic idea behind "rollback netcode" for fighting games?

Nice

💙

hey...I'm fullstack developer and i am planning to make multiplayergame using udemy or unreal in which i havent learned yet, and i want to make users create account and create or join a game and log data about the match on db but i'm new to game development and more detailed logic about implementation of online game can you help?

I’ve always called WAN a World Area Network. It just makes sense if the name is that… a World Area Network.

Roll back is the future, the problem currently is all modern languages have native floating-point representations for decimals as this has historically been better than fixed-point decimals for scientific computing but platform-specific quirks make floating-point code non-deterministic. Fixed point physics engines in particular. I imagine as new engines are developed from scratch this will be a requirement as it simplifies networking tremendously.

There is only one problem, fast efficient synchronization. Achieving that is very tricky.

Does anyone know the name of the game at 14:52?

Great video however it would be nice to see some code implemented

Good overview of networking but quite a few errors/assumptions

3:33 Awesome video but one small mistake. TCP stands for Transmission Control Potocrol. But as I said, still a really good and interesting video :)

Do I need to study and master computer networking in order to make multiplayer games?

Do you know what is the best part you don't have to relay in only one off those methods you by able to combine multiple off those multiplayer method if you want For example just because One game have lan Play for example it doesn't mean the don't able to have online servers as well One other example it's what I tried to achieve in the video game I tried to create the game I want to make I will have split screen and the option to play online or lan game at the same time for example in theory I will able to play up to 8 player's with 2 computers and my game I be host base but I will have some kind off server in the order people to able to connect online

@11:00 DRG is a great example of a game that doesn't use this right. You lag off cliffs all the time

It seems like peer-to-peer is executed in the LAN parties.

10:14 prediction data

Great explanation, however wouldn’t we be using ipv6 instead? If I made a game that had to use IP I’d opt for v6 if I could just to be future proof, and current

i miss lan games without internet or split screen now even single player game is online

UDP seems scary to me

I wish I knew how to make an offline multiplayer game for mobile

At around 8:00 you mention UDP connections being optimal for real-time physics, etc. Do you think we'll start seeing HTTP3/QUIC poking its head up, since it's a stream capable HTTP protocol that is based on UDP?

Love the content! Please speak a little slower with longer pauses, it'll help people (me) follow along and help with stumbling over or slurring words.

Ok, let's build our own Godot multiplayer game now

this video seem like a course in university which i have learned :v

This helped me understand why sometimes Rocket League behaves weirdly

I think you missed a very important point about udp. There is no guarantee that packets will arrive at all.