Firedragon

@Potatomachine A simple batch with this should work: <your path to the file>\steamcmd.exe +login anonymous +force_install_dir <atlas server install path> +app_update 1006030 validate +quit Example: E:\ATLAS\Engine\Binaries\ThirdParty\SteamCMD\Win64\steamcmd.exe +login anonymous +force_install_dir E:\ATLAS +app_update 1006030 validate +quit

Ich konnte den Fehler selber nie reproduzieren, normal sollte ein Wipe reichen und ich verlasse mich da ohne es selber zu diagnostizieren zu können auf Aussagen die von dritten getroffen wurden. Es ist natürlich möglich das eine Einstellung die vorgenommen wurde der Auslöser ist...

Das es vorkommt das Endbosse nicht spawnen habe ich bisher nur 2x gehört von denen die mit den Difficult Einstellungen hantiert oder den Endboss in eine Zone mit Inseln eingetragen haben. Ich konnte leider keine Fehlerdiagnose durchführen, nach neu setzen der Insel & wipe gings halt wieder. PS: 27XXX Ports sind bei vielen Spielen verwendet und eine Kollision ist leicht möglich.

I fired up your json file with my command line (changed to my ip): ShooterGame\Binaries\Win64\ShooterGameServer.exe Ocean?bIncreasePvPRespawnInterval=True?IncreasePvPRespawnIntervalBaseAmount=30?ServerX=0?ServerY=0?AltSaveDirectoryName=00?ServerAdminPassword=myownpass?MaxPlayers=125?ReservedPlayerSlots=25?QueryPort=57561?Port=5761?RCONEnabled=true?RCONPort=28001?DayCycleSpeedScale=0.500000?DayTimeSpeedScale=0.500000?NightTimeSpeedScale=2.000000?DinoCountMultiplier=2.000000?ResourcesRespawnPeriodMultiplier=0.700000?bAllowUnlimitedRespecs=true -log -server -NoBattlEye

%MapName%%GridLocation%?AltSaveDirectoryName=%AltSaveDir%?MaxPlayers=200?ReservedPlayerSlots=50?QueryPort=%QUERYPORT%?Port=%PORT%?SeamlessIP=%MACHINEIP%?MapPlayerLocation=true%AdditionalMapArguements% -log -server -culture=en -NoCrashDialog -NoBattlEye You can't use DOS var's as base args, put this in the starting line for every grid with correct data. Your sever doesn't even know what grid it is.

Did you check your json file? Maybe you forgot to set the name.

@JetFox another Feature would be awesome for your atlas updater. Adding check for ModId's version to restart the server (workaround for unconnectable atlas sever if mod is out of date).

You can ignore the two "gethostname" errors, the server runs when "Number of cores" is listed. If your server is not listed, either you did something wrong in your json file (using port twice / no homeserver / dyndns instead a real ip / duplicate atlasID and so on...), something is borking your ports or you are not connectable from the internet. Everyone else can see your server except you when running client from same pc? > missing loopback function!

Atlas runs not on my dedicated server, that's why i'm asking. Currently it works like this: rcon only works if it booted up properly and by accident B2 was on hold, BUUUT, today was an atlas update and that fixed it by itself.

Wenn die Firewall von Windows konfiguriert wurde (empfohlen anstelle sie abzuschalten) und kein Router davor hängt, dann kann sich nur in der Konfiguration ein Fehler eingeschlichen haben sofern eine ipv4 existiert. Ports dürfen niemals doppelt belegt werden, auch wenn RCON nicht benutzt wird, sollte man dennoch sicherstellen das es mit keinen anderen kollidiert und somit die Verbindung unmöglich wird (anlegen). Wenn du dich immer neu anmelden musst wenn du in eine andere Zone fährst, dann werden die Daten vom Spiel nicht weiter an deinen Client gesendet, sprich etwas blockiert die notwendigen Ports oder bei der json ist ein Fehler enthalten.

Welcher Router? DMZ / Exposed Host?

@JetFox is it possible to add an additional check if shootergameserver.exe responds / is fully started up? If you click by accident into the window from shootergameserver.exe it's on hold and doesn't startup properly. Real nice would be to send remote commands to atlas updater to force update or kill / restart a single grid without rcon. Any chance for this?

After latest Update it's working now.

Atlas Server Manager never wanted to run smooth, it has a gui and stores settings in registry, but fails in the purpose - keep atlas up to date... So far, this works very good even if you have to edit the config files by urself: How i manage our atlas server: redis as service auto updater to keep atlas bootet / up to date ftp for making edits to atlas json / ini files rcon to shutdown atlas server - all grid's (it starts up right away bcuz auto updater detects it is not running anymore) cobian backup 11 gravity (freeware) to backup atlas server related files every 3 hrs (saved folder / servergrid + .json / redis rdb - rotating 30 files backlog if there should be a crash)

Our server i7 2nd gen with 16 gb ram is at 75% usage for 4 grid's and starting up takes around 380 seconds. It's slow but stable so far hosting up to 20 ppl online at the same time (usage increases by time!). In compare, same server (for testing purpose before putting it online) on my gaming pc, i7 7700k with 32gb ram, runs smoothly at 35% usage (me and up to one friend testing). To calculate what hardware would be best, it depends on how many ppl will be online, how many islands per grid, how much they are going to build and stress your server. As even the official go by 4 grid's per ip (server) you should think about if a 5x5 would work on a single pc.

Das man einen bereits besuchten Server schnell findet liegt daran das der Client dazu Informationen hat. Atlas generell ist mit dem Listenserver sehr anstrengend, wenn er absolut nicht gefunden werden kann, liegt das hauptsächlich daran das er extern nicht angesprochen werden kann. Selbst unseren Server hatte ich nachdem die Favoriten durch ein Update raus waren erst nach mehreren Minuten suchen wieder gefunden. Wenn du die AtlasID änderst, legt die Redis Datenbank einen komplett neuen Datensatz dazu an der nicht auf den Saved Ordner passt. Wenn der Server mit der korrekten AtlasID online ist, kannst du probieren den selber zur Steam Server Liste hinzuzufügen (Home Server). STEAM > ANZEIGE > SERVER > FAVORITEN > HINZUFÜGEN > IP:PORT Wenn du dann aktualisierst und er wird ordentlich gefunden, probiere dich auf diesen zu verbinden.

When i tried it with a non home server grid it was like sakura said, but for home server it didn't match. Even after removing the whole saved folder for the home zone, spawning got broken.

Du meinst " TribeNameChangeCooldown " den du confen kannst auf die Zeit die du magst ?!?

There is a lot unknown data in redis database, in one of my tests even with empty saved grid folder where buildings and so on resides it simply didn't work and the grid itself lets me spawn in the middle of nowhere. Maybe it's just the playerdata itself that is the burden. Ex. playerbackup, id's such as home zone and ownerships for crafted things...

Like we know it from large fights against castles, the game is missing the tools for it for better pvp. We need war machines not only moveable by animal power on wheels, even humans should be able to push it to where it is needed. To make stone easier to breach, please add battering ram / tarant, huge catapults and burning tar.

It would be real nice to have poison arrows: Human: First hit slows down, second lets him sleep for a while if HP is 100, the char can wear off poison faster and it gets harder to stun the more HP the it has (not talking about the regular per arrow damage) Animals: A slowed down animal is easier to tame, if you send it to sleep, you can carry it to a place that makes it easier to tame it. Of course, more HP, the more it takes to stun it. The downside for using poison when taming is a huge loss in added lvlup bonus. How to get poison: Poison snakes drop it at rare chance

The limit for company size should be at max. by 150, for more they can have allies! A company should have initial 3 flags (Main Base) and expand only by 2 per member per grid to still make it possible to claim / fight for terrain. Stone should stay vanilla like it was for Ark, to prevent the fear they could barricade themself, add war machines like moveable battering ram / catapults (not only per animal, pushing too!) and make it realistic vuln against explosives (ballancing) and burning tar.

" GUIDES " is the wrong section.

To edit regis is out of question in such manner: If not having to do a full wipe, there might be a slight chance that it could work wiping a single grid.