search

Facepunch / sbox-issues

177 stars 12 forks source link

Expose Steamworks methods or allow managed DLLs in Standalone #6489

Open Arr-n-D opened 2 months ago

Arr-n-D commented 2 months ago

For?

S&Box

What can't you do?

I would like to implement my own networking solution with SteamNetworkingSockets, and since I plan on releasing on Steam ( if we get the green light) and I am a Steamworks partner, I wanted to use the Steamworks version.

I thought about adding https://github.com/rlabrecque/Steamworks.NET?tab=readme-ov-file, but I'm unable to use the Steamworks.NET.dll provided in the Release.

How would you like it to work?

I think having fully exported Steamworks methods would be the best solution as having multiple versions of Steamworks or C# bindings for the library would become quite a headache.

Another way would be to let us reference which DLLs we'd like to use in Project Settings.

What have you tried?

N/A

Additional context

No response

garrynewman commented 2 months ago

We need to establish a strategy here.. like what if you're targeting another platform in the future.

Arr-n-D commented 2 months ago

Maybe checkboxes in the export settings? Those checkboxes could be referenced as the platforms we're targeting, and from there we export the different platform dependent libraries?