Open Yazir opened 1 month ago
Yeah I am using a pretty hyper specific version of both steamworks and the facepunch setup. At some point my idea is to upgrade the steam works api to the newest version, and rewrite the facepunch library pretty heavily. Unfortunately the nuget package version is missing some undocumented functionality or is out of sync with newer steamworks version IIRC.
I assume this is the source of the libraries? If so it is worth pointing out in the readme.
That is the source of the steam binaries but the facepunch setup was pulled from a branch that was a significant amount ahead of their nuget release. Getting the actual source and documenting it is a good idea though, I'll see if I can track where I got it from.
While the example seems to work as it should, with its included libraries, updating Facepunch.Steamworks to a newer version (2.3.3 from nuget) produces a connection error. Steps to reproduce
delete
./Facepunch
folderadd
<PackageReference Include="facepunch.steamworks" Version="2.3.3" />
dotnet restore
in root directoryrun project, run exported project on separate steam account host lobby, connect to lobby on second account, lobby joining works, but it breaks on trying to estabilish socket connection
error:
SteamMultiplayerPeer.cs:373 -> AddConnection receives steamId equal to 0
Other than stability and feature completeness, it is useful to have facepunch as a nuget package, since exporting for different platforms is more streamlined.