2016-05-07, 16:40
(2016-05-07, 07:47)mikesilvo164 Wrote: The issue is those saying there menu reset cause of the update. I do not see how that is possible because even when you agree to reset it still requires a second confirmation from the user to perform it. This doesn't take into account people who do not wait for the update to finish and I have no idea if that would even trigger a menu reset by the skinshortcuts script.
For the record, it wouldn't. A menu reset is the deleting of the .DATA.xml and .properties file from userdata (wiki)/addon_data/script.skinshortcuts - there's no way a skin update could cause this, unless the new version of the skin calls the scripts inbuilt reset function (which is what I presume this skin does but, as Mike said, the script will then ask for confirmation from the user before deleting these files.)
Maybe I'm missing it, but has no-one captured a debug log yet...?