Ryan Pennington

This is a rather popular feature request (custom restart schedule) - I am thinking of a good implementation method for this and am going to make it a higher priority.

That was the issue, actually. Thank you so much

Alright, can you create a support ticket so we can check into this? Just reference this forum thread URL please.

What is your game server ID?

Game server ID?

Fixed!

awesome brotha thanks!!

I had the same issue, I had to uncheck the BattlEye option and then restart the server. Then recheck the BattlEye option and restart the server and it showed up in game as running BattlEye. 

It's probably something else. Please open up a support ticket or let me know your game server ID and I'll check.
 
    You've never had to do this actually. At server start/restart the server will automatically re-download and unpack every single mod. I know it sounds inefficient, but that's literally the only way to do it (Steam workshop is in it's infancy stage of being a reliable, automatable server-side product). So it's essentially mimicking directly the process of uploading an entire mod directory and .mod file to your server via FTP. To do a complete reinstall / wipe, you would simply just wipe all of the files/folders from /ShooterGame/Content/Mods/ without any need for uploading from FTP.   It appears that somehow the grabbing of files from Workshop -> downloading -> unpacking method is sometimes corrupted. This issue is prevalent with ARK client side as well, they even have a mention to that in their FAQ on their forums. Fun fact: we actually use the same C# code and built an executable off of code given to us from the server developer team at ARK to process our mod unpacking. So the logic/process is exactly the same as the client-side version.   I think when you are dealing with heavy disk i/o without proper verification (as it unpacks without verification) there is really no "check" to balance this out. If the disk i/o freezes up on the server and the unpacker executable crashes out (likewise with the client game itself) the mod unpack could be corrupted and lead to bad mod files causing wonky issues like this. Just one of possibly many imperfections with this process.   Sorry to get technical, but as you can see it's quite a difficult process to debug and following the aforementioned steps seems the best way to force it to work apart from any client-side issues that may be unrelated to the server mod files.

This is going to be toggled from the server control panel side. Working on it now.
 
EDIT: It's been added.

Well I was going to write a whole 100 word reply but since you removed it and realized what I ment I guess I can skip that part.
 
Just one question, Why have i been placed on moderator queue?
 
Anyways, i realized my mistake earlier today when i reread my first Tweet, "Will old customers have their prices raised?" Were it should have read Will current customers have their prices raised. Sorry if i disrespected you, Survival Servers, and any of its staff members in any way. This mistake caused many confusions as you have seen. Yesterday was a very stressful say for me yesterday so I hope you will forgive me. -Happy Customer -Ed
 
PS
Your control panel is very neat. Your servers have NO LAG. The setup is instant so its pretty cool.

This is going to be toggled from the server control panel side. Working on it now.
 
EDIT: It's been added.

Thank you for your response Overlord. 
 
My  issue has been resolved.
This parameter works for me
@ExileServer;@Exile -servermod=@A3XAI
 
It seems that there were problem on the CUP mod installation to the server, so it is causing the server not to start - if it is included on the parameter.

You can use admin commands via F1. The problem is you have to use RCON to give it to your in-game admin. So the dude has to be logged out that you're giving admin to. I have them log in to get their STEAM ID which is the really long number before their name in the RCON. 

ownerid (STEAMID) ("NAME") ("REASON")
 
That's what you type in minus the ( ). for the reason i just put ADMIN short and simple. 

EDIT: "Then use "server.writecfg" after entering the above command to save to the server."
 
if you give the person admin and they log back in after they logged out. it should say they have auth 2.
 
if you give them moderator or whatever it should say they have auth 1 I think.
 
Hoped this helped!

Because that mod overwrites the Dino content, they'd just have to simply update their mod for the new dino as they are released.
 
If the mod developer is slow on that end, then there could be a period of time between ARK releasing the patch with the new dino to the mod developer patching their mod with the new dino. Solves that dilemma Thank you for the detailed information!

The ARK server tool not having the Galli should not effect at all the ability for them to spawn.
 
I was able to force spawn / tame one on your server @pretresseneay
 

 
I am not sure why the DestroyWildDinos and then waiting for the dino to spawn isn't working.
 
May I suggest upping the spawn liklihood for that dino in your configuration?
 
EDIT: After running around for a bit on my force tamed Galli look who I ran into
 

Yes, thank you Ryan.  I was able to fix the Galli spawning issue yesterday.  There was a mod conflict.  I should've updated my post.  Gallis are now spawning correctly as you've shown and I'm very glad.  =)

Destroys all untamed creatures on the map. Useful for helping newly-released creatures to spawn.
admincheat destroywilddinos

nevermind..figured it out

Characters are named differently on solo and public servers. What you need to do is MAKE A COPY OF EVERYTHING in the SavedARK folder.
 
Just right click the folder, copy, then right click on whitespace and paste it. It will append a -copy version. If you screw up, you have your backup. Make sure you COPY/PASTE files from a backup on the same hard drive, else you just move them.
 
Next you need to find YOUR character ID. Your ID for solo is LocalPlayer.arkprofile and the ID for the online version is #################.arkprofile. The numbers are one of the versions of your Steam ID. You need to copy the name of your online profile character, delete the file (which will remove that character from the server), and rename the "LocalPlayer.arkprofile" file to that Steam ID name. You should then be able to use your solo character on the online server.
 
If you have more than 1 person already on your online server, you need to make sure you have the right character file selected.
If you need to find your ID there is an article from Steam for that: 
https://steamcommunity.com/sharedfiles/filedetails/?id=209000244
 
 
I also recommend making a backup copy of your server at least every couple days, depending on server activity. All you should need to copy are the profiles and 1 daily save, recommended minimum. You never know when there will be a "hardware issue" requiring moving your server where the person moving doesnt also move the save files.. Which happens.

It's a known bug, nothing to do with your server, they will lose dinos elsewhere too. Sometimes they fall through the world, you could check for them there, enable ghost and fly. Other times if they're in spots where rocks/trees are supposed to be they will vanish when the resource reappears. All I can say is, it's Alpha...

So, first question is are you running Oxide mod on the server?  If not, you probably want to!  Most of the things you want to do will be available as a plug-in.
 
Check out these plug-ins:
Better Chat allows custom chat settings, colors, etc.
Easy Airdrops gives RCon & Chat commands that call airdrops pretty much anyway you would want.
 
Adding your friends as admins/mods is a simple use of these commands:
ownerid "steamID" "player name" "reason(optional)"
moderatorid "steamID" "playername" "reason(optional)"
Then use "server.writecfg" after entering the above commands to save to the server.
A full write-up can be found at Oxide's website HERE.
 
You can also add people to usergroups, such as Admin, that can have it's own set of permissions with Oxide's permission system.  You can dive into that HERE.
 
Have fun!

Awesome! Thank you for the quick work as always! \m/,

The backups are now working again.