What I’m doing myself since a long time ago is launching the server with the -nosteam command line argument, that disables the steam client for the server, and thus it won’t show in server listings but it will allow you to run the game and the server in the same machine.
I just use the Direct Connect option and I type the local IP address of my machine every frkng time I need to connect
With this way it works and has been working since at least last April when I made the switch from single player to dedicated server.
Con of this -> Steam acievements don’t work.
Now, I’ve heard that there are options you could use, like making the server listen on a dedicated IP address, different than the public IP for your machine… or somehow changing which port the server uses, so it won’t conflict with the game client, because somehow that matters… but, In all honesty, I haven’t tried any of those methods so I cannot say for sure if they would work.
Someone said to me on Steam forums, that if you run the server as Admin, it also shouldn’t clash and thus the -nosteam parameter shouldn’t be required… but I tested that, and it still fails, server rejects the connection.
Tried server as admin, client as non-admin… server as non-admin, client as admin… neither did work.
Perhaps we need to wait for someone else to confirm if there are any other ways to proper setup the server to have it run locally in the same machine WITHOUT requiring other steam installation, account, whatever. (I don’t want to have to setup my account as family share, for example.)