HunterJDL

CMD > ipconfig > Look at IPv4 Address - It'll be something like 192.168.0.XX THAT is the IP you need to use in your port forward. It's the internal IP to that specific computer so the port forward knows which machine on the network it sends the connections to.

Hosting an ATLAS server is a larger project than people expect. Each server requires about 2 threads (1 core). At minimum I would suggest 3.6GHz with a boost up to 4.6GHz and higher. You'll want at least 4-5GB of ram each tile. If you have a small community look at hosting companies like LogicServers, Nitrado, SurvivalServers, etc. It's the more economical way to do things. 10-20 slots each server with 6 servers shouldn't cost you a lot. Keep in mind a lot of the hosting companies are struggling right now to get their act together because of how GrapeShot is conducting business with them, but it will be far less of a headache then trying to set up the server yourself. You'll also have support. If you need more slots and are thinking about self hosting than you are in some trouble. For 6 servers you will want a CPU that has at least 12 threads (6 cores). 32GB of ram should be fine but if you could, go for 64GB. Again, stick to 3.6GHz with a good bost of 4.6GHz or higher. For a hosting company I would recommend LogicServers. Mouseymars works his butt off and won't release anything less then a near perfect product. It may be a little more expensive then the other ones, but you'll get quality and someone who will not stop working until a fix is found. If one cannot be found, he won't BS and will be straight with you. (Join their discord). For self hosting I recommend avoiding OVH. Their machines are not good enough for anything larger than a 2x2. I'm with Reliablesite right now and they use actual server grade hardware, not desktop parts. The price tag is high but hosting an ATLAS server isn't exactly a small feat. This isn't a single server operation, you're almost literally hosting a small MMO. tl;dr LogicServers for hosting company, Avoid OVH for self hosting. You need better components for 6 tiles. It'll be expensive but check out sites like Reliablesite.

You can see everything in the game files if you look, it's how the spawn commands work. There does not seem to be anything related to alpha creatures in the files except the alpha buff. It's possible they did not use a separate creature for alphas and instead just had a chance for the alpha buff to be applied to a creature when it spawns. If this theory is correct, that means you will likely need the dev kit (or a .ini option if ATLAS has one) to disable them.

E5-2680 v2 may not have enough GHz to handle an ATLAS server. I'd not recommend lower than 3.6 with a boost of or past 4.6GHz. Expect 4-5GB of ram each tile. Go for 2 threads a server.

Gethostbyname failed() is normal, just ignore it ------------------------------------------ ATLAS requires a lot of ports. Game + Query - They look like 57561 and 5761 Seamless - Looks like 27000 Database - Looks like 6379 Leave the database port and IP alone. (As long as the database and server are running on the SAME machine. I don't recommend they are on different machines, it'll make this more difficult). If you have a router you need to port forward your query + game port PER each map. So your first map seems to be 57561 and 5761. Keep in mind, you also need to port forward +1 above the port. So an example below... Map 1 - 57561-57562,5761-5762 Map 2 - 57563-57564,5763,57564 (Make sure these ports match up in your map editor). I also port forward my seamless ports (27000-27003 as you have 4 maps) as it seems to help me with blank map issues. THEN you need to add the SAME ports you port forwarded, as a firewall rule in the inbound section. ----------------------------- You're second issue is your command line. If all 4 of your servers are saying "Server: 'Dragoons Gulches'" it's because you are not using the proper .bat arguments. ServerX=XX - This is the X coordinate of the tile in the map editor. ServerY=XX - This is the Y coordinate of the tile in the map editor AltSaveDirectoryName=XX - This is where this server instance will save it's files to. Each server should have a different directory QueryPort & Port - For server one use 57561 & 5761, then server 2 would use 57563 & 5763. SeamlessIP=XXX.XXX.XXX.XXX - This is the IP address the server is on Example for a 2x2 grid (4 maps) Map 1 = ServerX=0?ServerY=0?AltSaveDirectoryName=0?QueryPort=57561?Port=5761?SeamlessIP=98.181.215.73 Map 2 = ServerX=0?ServerY=1?AltSaveDirectoryName=1?QueryPort=57563?Port=5763?SeamlessIP=98.181.215.73 Map 3 = ServerX=1?ServerY=0?AltSaveDirectoryName=2?QueryPort=57565?Port=5765?SeamlessIP=98.181.215.73 Map 4 = ServerX=1?ServerY=1?AltSaveDirectoryName=3?QueryPort=57567?Port=5765?SeamlessIP=98.181.215.73 ------------------------------ I know it's a lot of information but running an ATLAS server isn't an easy task. In short you need to make sure your .bat arguments are correct PER server and that all of your ports are forwarded correctly and given firewall exceptions.

Project > Edit > Bottom right These are the IPs and passwords for the database. You can leave the IP to 127.0.0.1 if the database is on the same machine as the server. The ports can also be left alone. Make sure the passwords here match the passwords inside of the redis database config file. It can be found in AtlasRools > Redis folder.

Each area seems to take about 4-5GB of ram. You'll likely have a CPU issue long before a RAM one.

The maps in the map editor that have _PVE at the end have the ruins and mythical creatures.

You probably did not port forward or add firewall rules. That or you set the ip/ports wrong in the editor and the start .bat file.

You need to have a home server in your grid and active. Make sure your maps ID is unique and the name is simple. Instead of searching for the full name of the server, search for a single word. Searches can some times take up to 5 minutes to complete, and it may take the server being online for a minute for it to show up. Make sure you restart your game after you launch the server. If all else fails you can add the server to your steam server list and join it directly. Use google for how to do this.

-exclusivejoin in your startup line PlayersJoinNoCheckList.txt in ShooterGame/Binaries/Win64 (Create it if it's not there) Just add a steam 64 ID, one per line. You need to restart every time you add someone.

Hey all, I'm used to running ARK servers with ASM. I have my servers up and working and I know where to place the various config settings to get them to work but I've noticed an issue. Every time I update my server I use the command app_update xxxxxxx validate in steam cmd and it seems to reset all of the configs in the server folder. It's becoming an increasingly large pain to always have to re-add all of the various settings per server. I was wondering if anyone has a workaround for this or a better way to update the server files? Thanks in advance!