You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 2, 2025. It is now read-only.
Open your network object (which contains the NetworkServer, NetworkClient etc.) and add SteamSocketFactory component.
Setup your AppID and other settings as needed.
Assign this component as a reference to the Socket Factory fields of NetworkServer and NetworkClient.
Note: The default 480 (Spacewar) AppID is a very grey area, technically, it's not allowed but they don't really do anything about it. When you have your own AppID from Steam then replace the 480 with your own game AppID. If you know a better way around this, please make an Issue ticket.
Using the socket
Host
To be able to have your game working you need to make sure you have Steam running in the background.
Client
Clients need the SteamID64 of the host to be able to connect - it's used as the connection address.
Testing your game locally
You can't connect to yourself locally while using this socket since Steam doesn't allow multiple instances. If you want to test your game locally, you'll have to use UDP socket, for example, or use multiple machines.