Go, Go, Godot!
  • 0

Creating a UDP peer-to-peer connection

November 16, 2023

Creating network connections with Godot is simple — as long as you have the other party’s IP address, and there’s no NAT gateway involved. Unfortunately, that’s exactly the problem in most cases. You don’t know the other party’s IP, and these days, just about everyone is behind a combination wifi router/gateway/firewall with NAT.

Conceptually, NAT hole-punching is pretty simple, and this video explains how it’s done with just netcat.

In a nutshell:

  • listen on a particular port (e.g. 50001)
  • nc -u -l 50001
  • echo ‘hello’ | nc -u ipaddr 50001
  • echo ‘hole punch’ | nc -u -p 50001 ipaddr 50002
  • third party exchanges ip addresses

Putting it all together, player A (hosting a game) would require the game to connect to the directory server.

  • The directory server would list the game as something a player can now connect to.
  • player B (client who wants to join) will tell the directory service that it wants to connect, and will send its info
  • The directory server forwards the information to player A (host), player A will then send a packet to player B, and respond to the directory server
  • The directory server will then tell player B to go ahead and connect to player A.
  • Player B should be able to punch through to player A

With Godot, the connections from client to host would use ENetMultiplayerPeer.create_client(), which can specify the local port.

Here’s an older example of a signaling server: https://github.com/Faless/gd-webrtc-signalling/tree/master

gdscriptgodotnetworking
Posted in Godot.
Share
Previousgodot-matcha: Free multiplayer without a server
NextSuper Godot Galaxy Concept

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Related Posts

  • Strings
    December 17, 2022

    When not all strings are Strings. Detect bugs in your GDscript more easily with static typing

    One of the benefits of working with Godot Engine is that GDScript allows one to operate high level. GDScript is dynamically typed, so not even variable types have to be specified, but I would strongly recommend using static typing wherever possible. It can help with performance but primarily adds clarity when trying to follow the …

  • December 2, 2024

    Inventory System v1.18.1 available (and v2 progress update)

    I’m wrapping up development on version 1 of the Inventory System, which is currently at v1.18.1. All core functionality is in place, and it provides many quality-of-life features. The guide covers and walks through most of the code base, and the demo projects show off a lot of use cases. This first version has been …

  • February 10, 2024

    Inventory System v1.6 available

    Per feedback, we’ve exposed more inventory user interface component signals to make it easier to react to slot/item interactions with custom logic. New features: In addition, these bug fixes are included:

  • February 18, 2024

    Inventory System v1.9 available

    Another quick inventory system update. The Resizable Container Demo now includes preliminary support for controllers. Features: Additional bug fixes:

    © 2026 GoGoGodot.io. All rights reserved.