AMS2 Dedicated Server Tool / SteamCMD Support

At 60, you're going to talk to me about maturity. It's more a matter of your sharp suspicions.

 

i only asked about a bit more context, and you gave that to me, nothing more nothing less, not sure why you read more into it tbh

 

Why this fixation on me? You asked me to explain something I didn't even realize I'd done. A smiley face... Oh my God! Thank goodness I didn't hit a demon or something. Forget it, there are much more important things than me and my words. Go on with your thing.

 

No change with the browser pings, unfortunately.

Not a bad shout though. Still searching for a solution here - I have a league event planned in the next few weeks and I need this tool to work as it did a few weeks ago.

My last line in the log shows the following:

[DATE-TIME] INFO: Server startup finished: AppId 1066890, public IP (REDACTED), Steam id (REDACTED) ; switching to running state

REDACTED my addition. Nothing else afterwards.

It seems as if it's "hanging" on this instance - I never paid too much attention to the log readout, but I could have sworn there was a few more lines here before the ones that concerned players/Steam IDs joining the lobby.

Could be wrong, though.

 

might be worth to try the new direct joining of a server through a link option, make sure the game ISN'T running, adjust the ip address and port of your server, and also the password if needed.

The port you need to specify is the "hostport" as set in your server.cfg file.

For monitor users:


steam://run/1066890//-connect <ip>:<gameport> -password <password>

for VR:


steam://run/1066890//-connect <ip>:<gameport> -password <password> -forcevr
So as an example:
steam://run/1066890//-connect 132.156.231.28:26020 -password skill

Copy that url in a webbrowser, hit the enter key, and allow it to open steam, click continue in steam.

if that doesn't work, there has to be something in your network/port forwards or server.cfg that's causing issues, i would make a backup/rename of the server.cfg file, and pick a sample .cfg file from the config_sample folder, and rename that to server.cfg, and run a basic config to test if the issue is caused by the server.cfg or not.