Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

98 First Tame

About Xenithar

  • Rank
    Hide Armor
  • Birthday 06/13/1980

Personal Information

  • ARK Platforms Owned

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Solution: Buy a modern router. My Ubiquitis don't give me any issues and I purchased a Netgear XR500 for my home, but naturally I removed the horrendous OS that comes on it and stuck DD-WRT (Linux) on it. I am on a LAN with the servers and have never had an issue transferring between our eleven servers. Not once.
  2. Something appears to be broken. We have the New Year event enabled (-NewYearEvent on the command-line) for our servers but nothing is happening. At 12:05 EST I shut the cluster down and restarted our Island server. It said it was spawning presents at some coordinates. I used admin to teleport to the coordinates after logging in, and nothing was happening. It is still day on the server, but it is after 12am on the server clock, so it should be happening. Does this expect us to wait the entire day cycle until it triggers at night on the server? For now we rolled back in fear that the event is bu
  3. I could swear I had a dino from 2015 that had 255 in damage and I could level it more. Is that not right?
  4. SteamDB says the patch dropped an hour ago but my dedicated server cluster says I am up to date. What the heck is going on? I keep having down-time due to this insane delay between FORCING my client to update and then my servers claiming to be up to date! Get your act together, people! The game is six now and we're having problems I would expect from an alpha release! Redirecting stderr to 'C:\Games\SteamCMD\logs\stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK L
  5. Hmm, how do I get my level 633 rexes mutated to 1785? Jesus! On a serious note, I did not know of that setting. Thanks! We do not need it but it would be interesting to limit tames for a hard-mode server or something.
  6. The 450 cap is official only. I have level 633 rexes right now.
  7. I host ten servers, the first few are Windows and the rest Linux. Admin works fine. I use it regularly enough because I boot link-dead players so they can rejoin. Seriously, who thought it was a good idea to allow a player with no connection to not only stay active in the world for five minutes but also to not be able to reconnect until that time has passed unless kicked? No other game I have ever played does that. Anyway, admin is fine. I would check my configuration.
  8. Thanks for the info. Why has every unofficial server been excluded? They need to let us roll back our clients or something. OK, just tried again, as of 19min ago they pushed the update for us. Updating my cluster now. Try now, people.
  9. Well, the new update/ultra-nerf will not pull down to my server. I even did a clean install which turns out to be 337.16, and then trying to update does this. Redirecting stderr to 'C:\Games\SteamCMD\logs\stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK Logging in user '<hid my username>' to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Success! App '376030' already up to date. Press any key to continue . . . What is broken
  10. Had an issue since 337.15 dropped. Cannot update at all. Reinstalled both SteamCMD and Ark Dedicated Server. No dice. Why is Ark so broken since that patch bug that made the version something like 600? First it was three solid weeks of Vivox crashing, then 337.15 fixed that, and now we cannot update. Are the new versions only for official? Redirecting stderr to 'C:\Games\SteamCMD\logs\stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK Logging in user '<hid my us
  11. Just so people know, as soon as patch 337.15 came out, our cluster went back online like nothing was wrong. That was the patch which changed it back from version 678 to 337 where it should be. I wonder if the version number had anything to do with it. All I can say is that 337.15 was applied, we attempted to start the server again, and it started. We tried another server and it started. We're good again, but something was broken bad until 337.15.
  12. Your command SHOULD work. ./ShooterGameServer TheIsland?GameModIds=731604991?listen?SessionName=My_Server?Port=7777?QueryPort=27015?RCONEnabled=true?RCONPort=32768?ServerPassword=MyPassword?ServerAdminPassword=AdminPW?MaxPlayers=64?PreventDownloadSurvivors=false?PreventDownloadItems=false?PreventDownloadDinos=false?PreventUploadSurvivors=false?PreventUploadItems=false?PreventUploadDinos=false?AllowAnyoneBabyImprintCuddle=false?AllowCrateSpawnsOnTopOfStructures=true?AllowFlyingStaminaRecovery=true?AutoDestroyDecayedDinos=true?DestroyUnconnectedWaterPipes=true?DisableImprintDinoBuff=false?Ov
  13. Think I found the real issue. Since the dawn of Ark we have been able to do an install of the dedicated server in Linux and Windows, and then use symlinks in Linux or junctions in Windows to make clones of the installs so we could have one single install of the dedicated server and content, but MANY servers running from it. Somebody like me, who has ten servers, would need about 3TB of space to run ten servers instead of just under 300GB. Major difference. Doing a clean install and running works, but the configuration which has been supported from day one is now broken because Vivox, WHIC
  14. For starters, learn some basic networking. If the server is exposed to the WAN, I'd hope you're running Linux/Unix and a good iptables/nftables setup including dropping ICMP packets. If it traverses a gateway device, set THAT up correctly. Without knowing your setup though, advice is next to impossible.
  15. If that's the case then explain years of Ark working without UDP ports being forwarded at our colocation? We removed them after they disabled the ports. Do you really believe that, after all this time, they would not have issued a notice of correction if they forced it enabled? Come on now. As to your needing two ports, technically the engine uses many more than two, but the initial connection is formed ONLY on 7777 (or whatever you specify on the command-line). Try it. Forward only that port and see that it works. Once the connection is formed it is handed off to a random port, generally
  • Create New...