Game Development

3466 readers

12 users here now

Welcome to the game development community! This is a place to talk about and post anything related to the field of game development.

Community Wiki

founded 1 year ago

MODERATORS

Ategon

LiquidityC

Frank

Resources on Multiplayer Server Development using Godot 4.0 (feddit.de)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/gamedev

5 comments fedilink hide all child comments

Hi all :)

I'm interested in learning to develop a multiplayer game that is hosted with a single central server. With all the anti-hype around Unity, I thought I'd try out Godot instead.

I'm looking for learning resources on this. All I have found so far was centered around player-hosted multiplayer games, which is not what I'm looking for. Think about Diablo or Path of Exile where they have one or multiple servers managing the game and players. That is what I'm looking to learn doing.

I think more precisely:

database synchronisation
client synchronisation
interpolation for movement/effects
delta compression
server-side game state management

Game-wise, I'm looking to develop a multiplayer platformer.

I'm a backend software developer with a couple years in, so advanced guides are nothing I'm afraid of.

Thanks for your input :)

you are viewing a single comment's thread
view the rest of the comments

[–] o11c 2 points 1 year ago

            
              Sure, there are libraries and tools for some parts. But the question is: do they actually add value, or do they subtract it due to the cost it imposes to integrate them? There are only a couple parts where it is likely worth it (but even there, you'll need to understand what they're doing): the UDP reliability layer, the encryption layer, and possibly the event loop (but I say that mostly because io_uring is weird; previously I wouldn't include this. On the client side it isn't needed, but that depends on how much code you share between server and client). Packet framing and serialization are really easy to do yourself and most existing tools (which usually do generate code anyway) have weird limitations or overhead.
"should do more" is a general rule to prevent easy DoS attacks. It can mean packet sizes, it can mean computation, it can mean hard-coded timer delays, it can mean all sorts of things. Don't make it easy for a malicious client to waste shared resources. This is mostly relevant for early in the connection ... but keep in mind that it's possible for a malicious client to spy on a legitimate client and try to take over - that is, connections aren't actually a real thing (this applies even for TCP).