pet peeve really. when a new update comes along I am greeted with a restore defaults window as well as if i do not restore defaults certain buttons do not work, there functions do however just have to go to the menu's to do them.
I have no way of knowing what in my custom scripts are killing these features, and if I back up my scripts and add them after restoring defaults i get greeted with the restore defaults every single time I start kvirc.
it would be highly beneficial to know what needs to be restored maybe even see a diff(dispatch-conf as an example) type window. so that I can see the changes being applied to the scripts. also it might make sense to have user scripts and default scripts stored separately. so that any feature that is changed in an update is automatic and the user script is temporarily broken instead. with an explanation to the break given.

I'm sure i did some rambling but i think you get the jist of it.

basically yea I exported the parts I wrote to several kvs files, one alias.kvs file one popup.kvs. etc. each file only contained the parts I wrote. and then restore, and then import. if there was a way I could see the differences I could avoid the whole mess and instead rework what needs to be changed to accommodate the defaults.

yes thats exactly what I was thinking, just having diff or Kompare or equivalent for the default scripts. much like running dipatch-conf in Gentoo Linux.

I have no expectations of kvirc devs trying to figure out my gibberish coding