PerLevelStatsMultiplier Tool

Ark: Survival Evolved


There are 3 variants of the PerLevelStatsMultiplier setting in the Game.ini file for Ark: Survival Evolved. These settings are PerLevelStatsMultiplier_Player, PerLevelStatsMultiplier_DinoTamed, and PerLevelStatsMultiplier_DinoWild. They affect the corresponding entities' stat progression on level up. This tool will generate the code to adjust these settings to your liking quickly and easily.

While all of these stat adjustments can be applied to players, wild dinos, and tamed dinos, not all of them affect dinos. For example, Dinos do not craft, nor do they need water at this time.

Adjustment Notes: 1.0 is the default value. 0.01 will nearly disable stat progression, while 2.0 would give double the stat progression per level. So if you set Health to 2.0 you would go up 20 points when you hit the + for health on level up, instead of the default 10 points.

When Players, Tamed Dinos, and Wild Dinos level up there is a choice of a stat to increase. If you adjust these values you can control the amount of the increase. For example, you would normally get an extra 10 points on Health if you click the + for it on level up. Set the corresponding multiplier to 2.0, you'll get 20 points instead.

This tool can also be used for Single Player & Non-Dedicated Sessions. For information on customization in these situations and for information on what customization can do for you in general please see this page: Balancing Ark

For Players - PerLevelStatsMultiplier_Player

Health

Stamina

Torpidity

Oxygen

Food

Water

Temperature

Weight

Melee

Speed

Temperature Fortitude

Crafting

For Tamed Dinos - PerLevelStatsMultiplier_DinoTamed

Health

Stamina

Torpidity

Oxygen

Food

Water

Temperature

Weight

Melee

Speed

Temperature Fortitude

Crafting

For Wild Dinos - PerLevelStatsMultiplier_DinoWild

Health

Stamina

Torpidity

Oxygen

Food

Water

Temperature

Weight

Melee

Speed

Temperature Fortitude

Crafting

Your Custom Code - Game.ini

Installing The Code: Step #1

Shutdown the Ark: Survival Evolved Dedicated Server. The server cannot be running while you edit these files. Shut it down and make a copy of your 'Saved' directory and put it somewhere safe. This directory can be found in the 'ShooterGame' directory of your Ark Server. This will backup your world, character profiles, and current configuration files just in case. That is why I said earlier that it is important to read the instructions and information. If something goes wrong you can just restore your backed up files and be back to where you started.

Installing The Code: Step #2

Now we need to edit the Game.ini file.The first line in the box may already exist in your file. If so, omit this line when you copy your code and simply place the code below the line already existing in your file.

To find your Game.ini file, look in your server's directory for one of the following directories, depending on which OS your server box is running:

ShooterGame\Saved\Config\Windows\

ShooterGame\Saved\Config\Linux\

If you have already added code to this file, then there are two possibilities. Look at the custom code generated by our tool. If the first line already exists in your Game.ini file, do not copy that line. But do copy everything else and put it in your Game.ini file under where that line appears.

If the first line you see in our code box does not exist in your Game.ini file, then you can simply copy and paste all of the code and put it at the end of the file.

Remember, you must save and close the file after editing it.

As a final note, if you have already tried to setup these settings, then you must remove all of that code and replace it all with the code from this tool. Having information specified more than once can cause havoc with the server.

Installing The Code: Step #3

Now we have to test things. Make sure you have saved the changes to the Game.ini file and closed it. Then start your server and login to the game with your game client. Then disconnect from your server and shut it down.

Check the Game.ini file again. If the server likes the code, it will all still be there. If there was a problem with it, then the server will have replaced the file with a fresh copy that is blank.