The update procedure is to bring all of the ARKs down then start ARK1 let it update and initialize then bring the others back up en mass, as a precaution I have the wait timer on ARKs 2-10 set to 600 seconds so that if the Tower host gets rebooted ARK1 has time to pull any updates and initialize. Having the server binaries shared also means that when there is an update to ARK (and/or SteamCMD) it only has to be downloaded one time rather than 10. SteamCMD is in its original location per standard and the binary data for ARK is also in the default location. If they do release a new map it will only require changing the map name in the config and starting the container. Next I deployed 10 ARK server instances, why 10 when there are only 9 maps? Well, I assume that Wild card will have another map for Genesis Part 2 coming in the spring so I added a container to house it, currently it is configured as a 2nd Genesis1 map with all the correct ports and paths. If you don't want or care to use the dynamic configs, omit the ARK0 container and remove -UseDynamicConfig from the "Extra Game Parameters" of all subsequent ARK's you deploy. I ran this container first so that it would receive a predictable IP address (172.17.0.2:80) that is then used in the configurations of the remaining containers to add an entry to the hosts file (-add-host=:172.17.0.2) so that requests to in the game servers are pointed to the container running at 172.17.0.2. We are going to start with getting -UseDynamicConfig working and talking to our config file rather than the Official one out at, I know it feels like that should come last but bear with me.įirst we have a simple http server running by itself serving up the "dynamicconfig.ini" on port 80 on its container, this is mapped out to the host on 8080 and is not really needed but makes it easy to take a quick glance at tower:8080 to see what the settings are. Historical information left below (really go get the newer stuff from github) Go to the github, fetch the XMLs for however many servers you want to use in your new cluster, salt them to taste with your information (server names, cluster name, passwords, adminpasswords, ect.).
It and the accompanying XLM files should allow for a fairly simple stand up of a new ARK server cluster. With the inspiration (read thievery) present the A3C (ARK Cluster Companion Container). This will hopefully shed some light on the underside working bits of building a cluster of servers for ARK:SurvivalEvolved. I hope this helps others who - like me - don't really know what they are doing. I can now play in my old world from your server and it's a beautiful thing!!!! I had no idea the launchers could be different.
Ark steam api init failed windows 10#
The Windows 10 link opens the launcher that does not see the Minecraft Basic Docker.īut the Java link opens a different launcher that is specifically for Java servers. So when I saw these 2 listings in GeForce I launched them. I had been launching Minecraft from the Windows Start menu where I only have 1 listing and it does not say whether it is Java or Windows 10: However, today I saw this in my GeForce Experience screen: I had assumed there was only 1 minecraft launcher. It's been a while since I played regularly and this whole bedrock vs basic thing is new to me. My problem was I was thinking old school Minecraft launcher. Oh one thing, I don't connect to Multiplayer servers from the launcher (don't even know that this is possible.
It can be also possilbe that if you don't update the world from version to version (better speaking skipping a few major version) something breaks.Įventually you can send over your world and I try if I get it to work (if you need a place were you can upload the files please write me a PM). The logs look good, eventually something else isnt working.