So I ran across the following steam article(https://steamcommunity.com/sharedfiles/filedetails/?id=903819045) and was going to try and apply these changes to my server through the "Expert" tab. Although I had a few questions before proceeding,

Launch Codes - 1.I've already added the launch codes, so that shouldn't be an issue.

Engine.ini - 2. It mentions altering the Engine.ini file, I know this file isn't located within the ArkServers management interface, so I manually changed my own. I know by doing so, this won't affect my entire server, but will my server overwrite my Engine.ini file once I connect/restart my server? or does this file only live on my Local Machine?

GameUserSettings.ini - 3. Towards the bottom of the form post it mentions changing the GameUserSettings.ini file, I know I CAN'T do this via SFTP because it will just overwrite my changes once I re-upload my server files.The thing that throws me for a loop, is that [/script/shootergame.shootergameusersettings] already exists by default within my GameUserSettings.ini file on the "Expert" Tab. So if I try and add the recommended changes, will they negate each other since there are 2 instances of [/script/shootergame.shootergameusersettings] within my ini file, or does duplicate Brackets not matter? I wouldn't be adding [SessionSettings] SessionName=ARK #563569

[/script/engine.gamesession] MaxPlayers=70

[AdminPassword] Password= ServerPassword=

Just the [ScalabilityGroups] and [/script/shootergame.shootergameusersettings] section.

I'm aware that I'm trying to "overwrite" a lot of the default GameUserSettings.ini that are set by default within our Server Manager interface, but I'm just trying to verify that they won't revert or conflict with one another.

Sorry for my drawn out explanation, i'd be more than willing to elaborate more with screenshots if needed.

Short Answer:

Yes they'll conflict, and in some cases it could cause your server to choke on the ini file. To go a bit further unless you truly and fully know what you're doing with a LOT of the settings in that document I'd suggest not attempting to try and replace or overwrite any of the ini settings built by the server script. Think about it, the owner of this company has a very large incentive to do setup EVERYTHING in that pre-generated INI to ensure the best performance for their customer base. It's just good business to do so and cuts down on customer service requests and inquiries when the server just works as great as possible straight outta the box.

Longer Answer:

What you linked to is not server FPS improvements, but local game improvements.

https://steamcommunity.com/sharedfiles/filedetails/?id=903819045

Most of the commands in that link have to deal with graphics engine changes, of which the server code has zero implementation on the local system.

The only exceptions are going to be: -USEALLAVAILABLECORES - (the game will use all your CPU cores)

That command is proven not to work as the code architecture of ARK is a single thread / core program.

-lowmemory (the game will use only 4gb of your RAM) Will cause your server to crash at 4gb of ram instead of the 12gb / unlimited RAM your server is allocated for.

-low - (runs ARK as a low-priority process) -high - (runs ARK as a high-priority process) 1) Both of these contradict the other, neither are implemented properly in the Linux Build (which this server host utilizes)

The ini info that you've linked for ENGINE.ini is complete graphics ENGINE. It has ZERO to do with server stability.

Most of the gameusersettings.ini info is for local graphics as well, HOWEVER since you're throwing that into the gameusersettings.ini of the SERVER, ARK will FORCE any gated settings applicable to the local device onto the client.

For instance, if you use

MasterAudioVolume=0.107143 MusicAudioVolume=0.039683 SFXAudioVolume=0.409387 CameraShakeScale=0.037899 bFirstPersonRiding=False bThirdPersonPlayer=False

It will set all volume for the player at 10% master audio, 3% music audio and 40% SFX audio. The camera shake effect will always be 3% and players will not have their camera angle change when mounting dinosaurs and will not have the third person view.

If you are playing ARK on a potato. I shall repeat.... IF you are playing ARK on a potato, then put those settings on your PC to allow your PC to limp along while trying to play a AAA title that's poorly optimized on the local client.

If you're not playing ARK on a potato, don't force the rest of your community to feel like they are.

Awesome, all of your replies were extremely helpful.

I assumed most of what you replied with, but before I jumped to conclusions I just wanted to see if someone could verify.

I still get a tad confused on what changes server/local side when messing with some of these files, but you've cleared a lot of that up.

Thank you again,