GameNetworkingSockets VS GlosSI

Steam does have a NAT traversal/punchthrough service too. It's apparently usable without Steam according to their README on https://github.com/ValveSoftware/GameNetworkingSockets but honestly the only easy to use implementation I know is in Facepunch.Steamworks which requires a SteamID to initialize

Halo was mostly all about single player and early multiplayer/local multiplayer but their online netcode has sucked since Blood Gulch. Lots of games do networking horribly, I have been in gamedev making networking and I hate most of what people do. The ones that have a clean natting, based on enet style reliable UDP channels, RakNet style punch are better (RakNet was good until Facebook bought it). It has come a long way but also fallen back. Valve source netcode (on github) is probably the best and you can check it out here. They started with the best in Quake networking, then to Source.

There are some general APIs that are tied to Steam, like some networking stuff (even then there's an open source library), but the devs are not required to use any of those. If the devs chose to develop exclusively for steam and use their libraries, then that's their own decision.

Keep in mind that if you do go the GodotSteam route, there's GameNetworkingSockets from valve that doesn't have the requirement of needing Steam that you can use for releasing on other platforms. It has the same interface as the Steamworks SDK without requiring the Steamworks SDK.

Their UDP-but-connection-based game networking protocol can be used completely separetely from Steam (it also supports encryption). I think that does not include their relay networking solution, but still.. maybe it's helpful. They also have a TCP-like interface to make it easy to plug into an existing solution.

You can also use the non-Steam parts of that library in any game in case you don't just release on Steam (have a look at https://github.com/ValveSoftware/GameNetworkingSockets )

If you want to go the route of using a raw protocol and packing your messages yourself, I suggest to at least have a look at Valve's GameNetworkingSockets either for inspiration of what you might need or even to just use the library: https://github.com/ValveSoftware/GameNetworkingSockets

There is early NAT piercing support in Valve's GameNetworkingSockets. Check out:

You can also try Valve's GameNetworkingSockets with a serialization of your choice.

GlosSi

Sorry for the super late response guys. Haven’t been on reddit for a few days. Here you go: Thracky’s GloSC fork

I had issues using UWPHook because it wouldn't focus correctly in Gamescope. I switched to Glosc v 2.0.8 and it works perfectly. https://github.com/Thracky/GlosSI

If you use this forked release: https://github.com/Thracky/GlosSI/releases/tag/2.0.8

I installed this version on the host PC, added the UWP game as a shortcut & run it from the client PC with a controller connected.

If you're playing the gamepass/uwp version of the game, You can get the controller to work by either adding the game to your steam library using https://github.com/Thracky/GloSC/releases/tag/2.0.8 or possibly using DS4Windows from https://github.com/Ryochan7/DS4Windows/releases