2019-12-03, 21:20
(2019-12-03, 19:04)mikeSiLVO Wrote: I am saying that if you are doing it right then it is impossible for one to work when the other does not...
Whilst you are almost certainly right (and speaking from the perspective of what the script does, as opposed to your own perspective of how the skin interacts with it - the perfect mix, right
) It is - very broadly - possible for a change to the addon.xml file - which, obviously, wouldn't be directly related to the Skin Shortcuts script - to cause the issue Roby is seeing. The script has to parse the whole addon.xml file to work out where to write the includes.xml file. So, if there was for example a change to the various international descriptions provided in the addons.xml file (which remains the file causing the issue, as of roby's most recent debug log), if there were a encode/decode issue with with this file, the problem Roby is seeing would occur. (Though I think its fair to say this issue is still likely to be more widespread than the one user, if this is the case)However, I'm a huge fan of occums razor, and the most likely explanations remain not running an 100% official Nox Silvo build (which would have its own addon.xml file), or - as you say - an issue installing from git, and so the reason the script can't parse the addon.xml correctly is because it either has the wrong permissions (Skin Shortcuts only needs read permissions, so unlikely), or because it is malformed in some (unlikely if git/repo versions are being used), or because the file isn't actually in the exact location the script expects (possible if not installing from Git correctly...).
