Config stuff breaks default bukkit config

[Maxopoly]

saveDefaultConfig should just fail silently, but with CivModCore it will always save the yml structure back, which means it actively removes comments, formatting etc. Also if the file is not parsed properly it will sometimes delete the whole config.

It seems like additionally it's not saving the normal default config if no config exists previously (when starting plugin for first time).

[ProgrammerDan]

Any objection to just gutting this and using the annotations to wire up a Bukkit-standard "default config" behind the scenes, which gets overridden by package config which gets overridden by plugin-folder config (e.g. like normal)?

[Maxopoly]

Not from my side

[ProgrammerDan]

I'll just assume no objection b/c it should be transparent to any plugin that utilizes this. I'll get on it.