BentoFox

I"ve found something that's definitely not cool about this program. every time you open the app and make any change to the grids, it clears the whole "Batch Files (to run atlas manually)" folder, including files I've placed there myself. That way it also overrides the batch files I require to start my server, as I have a non-static IP and need to resolve my DNS before entering the IP in the server launch editor. Additionally, there is no way to configure something like this in the program; it would be nice to be able to script the actual launch method of the program so additional batch commands can be executed before launching each server instance. In my particular case, I need "for /f %%a in ('powershell Invoke-RestMethod api.ipify.org') do set PublicIP=%%a" to be executed before the server instances are started. And that "%PublicIP%" needs to be set as the SeamlessIP launch parameter.

@SparcMX Hey there, I've been trying for hours to get the maps to work but they end up grey no matter what I do. One thing I noticed is that the server windows show the seamlessIP as the local loopback. I've read elsewhere that this should be set to the public IP of the map image hosting machine but I don't have a static IPv4 and rely on DynDNS. That aside though, I've found no setting to actually change this IP as the actual server start command is not exposed. Is there currently a way to overwrite the SeamlessIP parameter from the server start command with a DNS address? Or is it fine being set to localhost if there's only one hosting PC?

@BurnerZA Probably a month too late, but the problem is that ASC corrupts your "ServerGrid.ServerOnly.json" when you save or export on a clean server. When you open that file you'll notice that at the end it says: "DatabaseConnections": null Replace that with the code below and it will work. (change pw / port where applicable) "DatabaseConnections": [ { "Name": "Default", "URL": "127.0.0.1", "Port": 6379, "Password": "foobared" }, { "Name": "TribeDB", "URL": "127.0.0.1", "Port": 6379, "Password": "foobared" }, { "Name": "TravelDataDB", "URL": "127.0.0.1", "Port": 6379, "Password": "foobared" }, { "Name": "TerritoryDB", "URL": "127.0.0.1", "Port": 6379, "Password": "foobared" }, { "Name": "LogDB", "URL": "127.0.0.1", "Port": 6379, "Password": "foobared" } ]

In my case this was caused by the ServerGrid.ServerOnly.json somehow containing an empty array of database connections, I filled them in from a different server on another machine and the issue disappeared for me. For others with a similar issue, I've posted the default values below. "DatabaseConnections": [ { "Name": "Default", "URL": "127.0.0.1", "Port": 6379, "Password": "foobared" }, { "Name": "TribeDB", "URL": "127.0.0.1", "Port": 6379, "Password": "foobared" }, { "Name": "TravelDataDB", "URL": "127.0.0.1", "Port": 6379, "Password": "foobared" }, { "Name": "TerritoryDB", "URL": "127.0.0.1", "Port": 6379, "Password": "foobared" }, { "Name": "LogDB", "URL": "127.0.0.1", "Port": 6379, "Password": "foobared" } ]