asofold 3d73a54fcd Fix faulty config notifications. ... The per-config-path notifications would keep showing up, even if you removed the paths, then run 'ncp reload', then alter any of them and run 'ncp reload'. To fix this, the configversion.created value is set to the current build, if no config warnings are there - which is the same, as what the notification suggests as an alternative to removing the paths and running 'ncp reload'. To do this, isConfigUpToDate had to be moved from Updates to ConfigManager, which makes more sense anyway. In addition the 'created' and saved 'values' are set to the biggest thing found, instead of the prehistoric static value. Further a negative 'created' value will not be overridden anymore, allowing to silence the config notifications forever. Not necessarily recommended for the general case, but it can be useful/necessary with maintained blueprints, e.g. with administering multiple servers. One of the next steps will be to remove the DefaultConfig.buildNumber in favor of setting a build number for each and every path added. All provided we don't run into nasty issues here. Another follow up could be to create an extra registry/config log file and write all the values there, and only print the first 5 in ingame chat.		2017-04-12 20:44:26 +02:00
..
src	Fix faulty config notifications.	2017-04-12 20:44:26 +02:00
pom.xml	Add a dedicated compatibility module for 1.10.x (1.10 R1).	2016-12-27 23:36:03 +01:00