-
-
Notifications
You must be signed in to change notification settings - Fork 305
Uploading to Steam
Pretty much this video https://www.youtube.com/watch?v=rK5Fr5hhslM
It is an outdated video, but it works great, and is a far better visual aid than this text.
Make a build, but make sure the build's name, is the same as what steam expects. See the image below. I name my steam builds "[GameTitle]Steam.exe"
Tools>ContentBuilder>Scripts
Should have different contents than you. You should have 4, instead of 2.
Regardless, just replace the appID with your game's appID in all these files.
And for the depot, do the same (find depot ID by going into your browser and your game, then SteamPipe>Depots)
It should be your id + 1 by default.
Don't forget to rename them, to match the proper ID btw!
Everything else is pretty much the same. It could be faster, and he does shill his game a bit much, but the video fully explains how to build.
Please note that steam depots are like git. They notice diffs, and so, only the first build takes time to upload.
So, the process to test should be pretty smooth.
If you did the integration with Steamworks.Facepunch, try logging out and logging in Steam, before opening the game. You should see the steam layout :)
Getting Started
Network Contract Wizard (NCW)
Remote Procedure Calls (RPCs)
Unity Integration
Basic Network Samples
Scene Navigation
Master Server
Netcoding Design Patterns
Troubleshooting
Miscellaneous
-
Connection Cycle Events
-
Rewinding
-
Network Logging
-
Working with Multiple Sockets
-
Modify Master and Standalone servers
-
NAT Hole Punching
-
UDP LAN Discovery
-
Offline Mode
-
Ping Pong
-
Lobby System
-
Upgrading Forge Remastered to Develop branch or different version
-
Forge Networking Classic to Remastered Migration Guide
-
Script to easily use Forge Networking from sources
-
Run Two Unity Instances with Shared Assets for Easiest Dedicated Client Workflow