[Dedicated Server] game.ini file is being ignored

[Suros:/#]

Like the title says, my game.ini file is being ignored. I recently updated with steamcmd, so all I can think is that the update has screwed something up. Verified the path to the file was still right, and all the contents are the way I left them, but now all rates minus the things I've set in the command line are back to defaults.

[Gran]

People don't like to hear this, but if your game.ini gets ignored, it's most probably that you screwed up somehow.

[Suros:/#]

Originally posted by Gran:

People don't like to hear this, but if your game.ini gets ignored, it's most probably that you screwed up somehow.

I fail to see how I could've screwed up. The file has been working for a good two weeks. Upon doing the update, it now doesn't work. It has worked perfectly fine after several of their updates.

[Nutcutt3r]

So just throw it back in and away you go.

[Suros:/#]

Originally posted by Nutcutt3r:

So just throw it back in and away you go.

I never removed it in the first place.

[Gran]

If the update would have caused that there would be a "Riot" in the Main and Bug Section of the Forum, but since you seems to be the only one with that problem, probably not the updates fault.

And the only time an update did something like that it happen to everyone, not only a selected one.

[ZánÐêr]

post the folder path to the game.ini you are using. There are a couple different ones and yo may be using the wrong one.

Also, copy/paste the contents of your game . ini here ( take out any passwords you may have in it, if any.. you shouldnt bu thtought i would add it )

if something is wrong near the beginning of the game ini it may not read anything after it.

[Suros:/#]

Originally posted by Gran:

If the update would have caused that there would be a "Riot" in the Main and Bug Section of the Forum, but since you seems to be the only one with that problem, probably not the updates fault.

And the only time an update did something like that it happen to everyone, not only a selected one.

Let's assume I did screw something up. What could get messed up by stopping a working server, checking for updates, and starting it right back up? I didn't even touch the config files until I saw that everything was at stock values unless it was listed in the command line.

[ntengineer]

I saw something on survivetheark.com about a similar problem. The solution was to move the files out of the folder, start the server and let it create fresh ones, then stop the server and copy back in your customized ones, and start the server again.

Try that and see if it works.

[Suros:/#]

Originally posted by ntengineer:

I saw something on survivetheark.com about a similar problem. The solution was to move the files out of the folder, start the server and let it create fresh ones, then stop the server and copy back in your customized ones, and start the server again.

Try that and see if it works.

I'll try that. Thank you for the helpful info.

[eliteangler]

Originally posted by Suros# Linux:

Originally posted by ntengineer:

I saw something on survivetheark.com about a similar problem. The solution was to move the files out of the folder, start the server and let it create fresh ones, then stop the server and copy back in your customized ones, and start the server again.

Try that and see if it works.

I'll try that. Thank you for the helpful info.

That is what I have had to do in the past.

[Gran]

Originally posted by Suros# Linux:

Originally posted by Gran:

If the update would have caused that there would be a "Riot" in the Main and Bug Section of the Forum, but since you seems to be the only one with that problem, probably not the updates fault.

And the only time an update did something like that it happen to everyone, not only a selected one.

Let's assume I did screw something up. What could get messed up by stopping a working server, checking for updates, and starting it right back up? I didn't even touch the config files until I saw that everything was at stock values unless it was listed in the command line.

That i don't know, how could i? I neither know how and when you updated, neither do i know how you start your server. I don't know nothing about anything of your Stuff except that you claim the updated messed with your game.ini, which is nearly impossible given the fact that we all get the same updates and neither of the ~18k Admins had reported a similar Problem with any of the 254 subupdates.

[Suros:/#]

Dumping the old files did the trick. Thank you to those of you who gave helpful info.

[ntengineer]

Originally posted by Suros# Linux:

Dumping the old files did the trick. Thank you to those of you who gave helpful info.

Awesome!