I’ve got this very simple problem and a proposition. Basically refactoring AppSettings.
Maintaining global application settings & user settings separately. In different files. Whereas the global application settings would really have nothing to do with JME. But JME has nice handling of property files through AppSettings.java which I would like to use. And it is usable right now as well, just avoid generating the defaults. But hygiene!
Strip AppSettings of these generic property file handling stuff (saving, loading, reading…) and instead let AppSettings extend this newly founded utility class. Maybe not a very common use case but not a big change either and totally non-breaking one.