.ini Issues with Modify Server Config

[ABYAY 1]

Hello, I've used a private ARK server for quite a while and ever since the recent update affecting player experience (ascension) there has been a .ini issue with my server. I've done a good bit of troubleshooting as is which will be explained below along with the problem.

 

On my server I have compressed the dino experience curve to allow much faster leveling and I've also increased the level cap along with that, only for dinos. The player experience is unaffected. I use some basic increased modifiers as well as a simple stack mod. Now, onto the issue: Ever since the update a character can not go beyond level 85. It just caps at that point and some engrams remain forever locked. I ran some general troubleshooting such as removing the mod and restarting (didn't do a thing) and then I reset the modified configuration completely. Even with the mod this fixed the experience problem for the player but I had to reset all of the settings again. After doing so the problem came back and my character was reverted to level 85. I looked into the .ini and here is what shows up that starts looking strange (well, at least the beginning, full .txt file is posted as a .txt file as an attachment)

LevelExperienceRampOverrides=(ExperiencePointsForLevel[0]=5,ExperiencePointsForLevel[1]=20 --

Just as a heads up, this is the player experience and the game suspects that this setting is being overridden. I did not turn on an override for player experience, only for dinosaur experience. The adjusted dinosaur experience shows up in the .ini and the dinos react accordingly so that is working fine. Whenever I change the Dinosaur experience to revert to the default this part of the .ini is gone and the player level works as normal. Is it intended for the game to try to detect player experience overrides if you change the dino experience overrides? Right now this is causing some issues ever since the recent patch and I didn't know if this has been reported. Just for comparison I will provide a game.ini of the server whenever I leave the dino experience as a default and as mentioned before, a .txt of the game.ini when the dinosaur experience is affected.

 

 

Experienceinierror.txt

Serverinidefault.txt

[GamerPerfection 5]

What is your max Survivor level set at? Is it at 100? If so then 85 cap would be correct.

 

For example, I have my max Survivor lvl at 150 and the cap pre-ascension is 135.

[ABYAY 1]

Thanks for the reply GamerPerfection. This isn't really an issue with what the maximum survivor cap is since it works normally IF the dinosaur levels are untouched. My character is level 99 and if I don't have level cap modifiers changed, this level will remain at 99. However the moment I add in a modifier for the dinosaurs, not the player, the cap immediately falls back to 85 for the player. This is because the settings is projecting a modified stat level for players even though it's not supposed to do this, at least in theory.

 

I could try a workaround that adjusts the maximum player level to 115 and see if that provides a "patch" to the problem, will update this post tonight.

 

Edit: Unsurprisingly adding 15 levels blocked off by 1 experience point does alleviate the issue and allows leveling up to 100. Again as stated though this is merely a workaround. It'll work but if this is a bug with the way the server config works then I'd like it to be more known.

[koltec 3]

its not a bug with the new ascension wild card put in  the last 15 levels are gotten by ascending

[ABYAY 1]

In a normal state, if you don't affect the levels with any of the server config settings, then the game .ini will show no override for levels and everything functions normally. However, please tell me why the button in the attached picture, when toggled, is triggering an experience override in the .ini for the player level. I know it shows the player level adjusted now and that's because I made the right changes. However the highlighted setting should not be triggering an experience override for the player in the .ini unless this is a strange intention that the ascension change now negatively affects and/or confuses server owners like myself initially.