I've never seen config corruption in foobar. I might have some strange things with playlists but always after manual manipulation over files in config folder and I was never sorry for that. I even used several plugins that were unstable and foobar crashed many times but I've never experienced anything worse than lost of unsaved playlist. If you have any errors then check you HDD for bad sectors and RAM for faults.
Do I seriously need to remind people how often the OS and programs crash?
Quote from: attachmentDownload on 06 November, 2015, 03:00:31 PMDo I seriously need to remind people how often the OS and programs crash?Please do. Sounds like you have a faulty setup that you should investigate.As for the topic, anyone in OPs shoes can:[pleaseSomehowGetFutureReaderAttention][blinking_text]1) investigate what causes bad shutdowns and corruption as neither of those are normal, especially at the frequency OP seems to suggest 2) use foo_jesus to regularly back up their stuff (as far as foobar is concerned).[/color][/blinking_text][/pleaseSomehowGetFutureReaderAttention]
It's a pity that foo_jesus's default setting of "Files and directories to back up"Quoteconfiguration;playlists;index-data;theme.fth;PlaybackStatistics.datis outdated now, and that's not mentioned anywhere. Instead it should beQuoteconfiguration;playlists-v1.3;index-data;theme.fth;library
Otherwise, since you can easily extract components, it should be possible to act as a maintainer for now and upload an updated version.
This would be illegal without the permission of yirkha in the first place
i have no idea how it was done but romor updated foo_softplaylists with a new last.fm API key when the built in one stopped working and caused the component to crash. this happened before the source was published.
Quote from: Kohlrabi on 08 November, 2015, 04:46:01 AMOtherwise, since you can easily extract components, it should be possible to act as a maintainer for now and upload an updated version.This would be illegal without the permission of yirkha in the first place and you also cannot just extract a component and update some settings. You need to have the source code of the component and recompile it with the new default settings.
I guess the settings are plain text?
It left foobar entirely unaffected.