Reply to thread

Message: <blockquote data-quote="MJGraf" data-source="post: 1116607" data-attributes="member: 17886">Perfect, osre! That's how it is currently already done in some parts of the code (i.e. when the setting is loaded, in the next line of code, we just write it to disk). The right solution is imho that when you load a setting and it does not exist on the disk, yet, the SettingsManager should automatically save the file with default settings to disk. That way we can remove the workarounds in the code where we load and manually save...It would be very strange if this side effect is caused by the ServerSettings.xml file - maybe if you have done your patch in a way so that all settings files are written to disk (not only ServerSettings.xml) but even in this case, the behavior described would be a bug...</blockquote>