Facepunch.Steamworks VS Steamworks.NET-Test

This link might help as it has a couple examples: https://github.com/Facepunch/Facepunch.Steamworks/issues/261

- I'm using Facepunch as the steam library - it's a nice wrapper around the steam SDK, which can be a little annoying to use directly.

If you are using Unity, have a look at the facepunch wrapper for the Steamworks SDK. It's pretty nice.

I’ve been using this. Very easy to use, has p2p support. https://github.com/Facepunch/Facepunch.Steamworks

I also tried to integrate Facepunch.Steamworks, but it didn't seem to be working on Apple Silicon (if I understand correctly). Facepunch's last release was also 2 years ago. Since the latest Steamworks.NET was released a month ago, I believe it's currently the way to go (despite the clunkier API) if you're trying to integrate Steam into your C# Godot Project.

Facepunch.Steamworks 2.3.2

Steam's latest networking API has built in support for using relays to hide p2p IP addresses. He was using Another Fucking Steamworks C# Implementation which appears to be based on the older network apis.

Depending on how you check various things, I'd recommend you use Facepunch.Steamworks which is free and available here: https://github.com/Facepunch/Facepunch.Steamworks

You might also find something useful in Steamworks.NET's SteamInputTest

Hey! So pretty much it's the Steam Inventory Service + Inventory Item store. On the Steam side of things you setup the inventory service for all of your in game items (which is really just JSON) and then in your game, you write code that interacts with the service. If you're using Steamworks.NET, have a look at this github repo for implementation examples. The Item Store is purely the UI aspect of it, so for our game, that would be this page.