JetFox

Hi Buccaneers, College life caught up with me along with other more profitable freelance work ive been doing. I checked into that crash its actually steamkit problem that was hotfixed and I never recompiled with the hotfix yet. Currently in AZ for a week vacation. Best Regards, JetFox

Yes but if you open a command prompt can you ping your external ip? I thought you needed a loopback ip

I don't remember if you can connect to your own server if its on your own network.

if you manually enter the configs in the save folders, steam updater wont override those, then defaultgameusersettings becomes never needed. ehhhhhhh, maybe.

If you accidentally click in the window just press enter and itll resume bootup, maybe reboot grid option later

Delete the server.pid files in atlas before launch probably would fix it.

2.0.3.0 out

Check back in like 12 hours im catching some sleep, I'll post a dl for a private build but i wont keep it up to date for every early release.

Is there a reason why 127.0.0.1 shouldnt work?

Fixed in 2.0.2.0 Fixed in 2.0.2.0 (Backups now work again) Uhm, it connects to whatever you have set in the config file.

Confirm your server.cfg matches new parameters that moved to top.

Try now

Fixed

Try reinstall steamcmd? Im aware of that bug, working on it.

V2.0.0.3 Configuration Change: GameServerPath moved from settings-template.json to the top so you dont have it for every server... Configuration Change: SteamUpdateScript moved from settings-template.json to the top so you dont have it for every server... Crash Detection on RedisDB, if a server crashes it wont boot up the servers til redis is back online.