[User Retest] Saving Issue

thcue

thcue

CAT Moderator
JFF Member
Mar 7, 2017
65
10
0
2' From my Computer
While CAT is up and Running the CAT program will remember all settings and set them in the correct INIs

However if you shutdown the CE server and the CAT tool and reopen CAT will reset itself to a default state, but your correct or previous settings are still in your INIs. If you put or save settings in the reset CAT you will reset your INIs to the new settings you use.

Workaround. Never Close your CE server with CAT not running.

Items not saving are:

Server Name *FIXED
Port number *FIXED
Max Users *FIXED
Allowed Regions *FIXED
Can Damage Structures
Drop on death (equipment)
 
Last edited:
Some Features now saving in V019*
Also The Items you choose will save in INI's just will show default in CAT and not read your previous settings.

Items not saving are:

Drop on death boxes
Misc Settings boxes
Port number
Max Users
Allowed Regions
 
Last edited:
The saving issues is after you hit save. Stop the server then re-open settings the two will not be saved and will be unchecked again in default positions.
 
thcue said:
The saving issues is after you hit save. Stop the server then re-open settings the two will not be saved and will be unchecked again in default positions.
Click to expand...

Ok, I'm pretty sure this is a CE server issue. So... delete any other "Drop on death" settings directly from the INI file. Meaning the old ones we don't use now, the toolbar and inventory ones. Then it should work as expected. It seems that the CE server stops reading any new properties if it encounters one it doesn't know how to handle or something.

But I was able to reproduce this, and when I removed those settings, its working as I would expect.
 
I think I fixed the Issue here. I moved DropEquipmentOnDeath=True from the bottom of the ini file to the top under password. Everything saved correctly. I guess the setting DropEquipmentOnDeath=True does not like to be at the bottom of the file.
 
thcue said:
I did a complete wipe of ServerSettings.ini and let CAT save the file. The last two options in OP are the ones not saving.
Click to expand...

Save them with CAT, close CAT.
Then open the INI file in a text editor (I use notepad++).
Make sure those values exist and are what you saved with CAT.
Now run the startserver.bat file in the CE folder. See if those settings get removed. If they do, it is the CE server removing them because it found an issue in the INI file, and stopped reading it. This is why when you had the setting at the bottom of the file before, it didn't work, but when you moved it to the top, it did.

So there is "something" bad in the INI file... so frustrating.
 
thcue said:
Just did what you just said yes CE removes it Not CAT
Click to expand...

Yeah, so my current theory is that there is a problem with a setting that causes the CE server to stop reading the INI file and then revert to defaults for the remainder of the settings. If you can, send me a copy of your INI file (clear any passwords, etc), so I can compare it to mine and see what I can see. There has to be a bad value somewhere in there I think.
 
I got it all solved. If them two settings are true then CE will remove the lines from the INI. It's default for the game. So the only Option you can do is set to False then they will stay in the INI and force it to false.

So whats going on is CAT does not see the Command as True so it removes the check box. But if you save it with no check box it sets to False. Just need to change the Check Box to Checked for Default and Unchecked for False.
 
thcue said:
I got it all solved. If them two settings are true then CE will remove the lines from the INI. It's default for the game. So the only Option you can do is set to False then they will stay in the INI and force it to false.

So whats going on is CAT does not see the Command as True so it removes the check box. But if you save it with no check box it sets to False. Just need to change the Check Box to Checked for Default and Unchecked for False.
Click to expand...

This is actually a bigger problem.

Checking for the existence of the key is annoying... really shitty way for them to code it... otherwise, why have a value set at all? Just a key is all they'd need. The fact that it sets (and saves) with a false value... they should be doing the same with a true value. Really annoying. I need to rethink a lot of things now.
 
Trekkan said:
This is actually a bigger problem.

Checking for the existence of the key is annoying... really shitty way for them to code it... otherwise, why have a value set at all? Just a key is all they'd need. The fact that it sets (and saves) with a false value... they should be doing the same with a true value. Really annoying. I need to rethink a lot of things now.
Click to expand...

What is weird they don't do it to all the values.
 
Ok, I figured this out. I need to rewrite a bunch of code, but I'm pretty sure I can solve this.

What is happening is... if a value is in DefaultServerSettings.ini and also exists *with the same value* in ServerSettings.ini, the key/value in ServerSettings.ini is deleted. Doesn't matter whether or not it's true or false, etc. It just has to be both the same key/value match. This is better than the other possibility, so... like I said, I need to re-code some things now.
 
I think I have this wrapped up, needs more testing of course. But the basic idea I went with is this:

If there are settings in the DefaultServerSettings.ini file they are copied to the ServerSettings.ini file. Then, to prevent the problem from happening, all setting sin the DefaultServerSettings.ini file are commented out (I was going to just remove them, but I figured that'd be rude). =)

Anyway, so what you end up with is a ServerSettings.ini file, with all possible settings in it, and by commenting out the items in DefaultServerSettings.ini, they are ignored. So there is only one "source" for settings.

If new settings are created and added to DefaultServerSettings.ini, they are automatically imported when you start CAT and added to ServerSettings.ini. So you won't lose settings, etc. Anyway, still needs testing, but working so far on my machine.
 
You must log in or register to reply here.
Top Bottom