Well, that escalated quickly...
Dude, chill. xD
Let me make myself clear, there will always be errors with skins that are meant to work in conjunction with other skins.
There are two types of errors, generic ones that can be disregarded because thats how the main software handles things.
And there are bad errors, that of course need fixing.
You can fix a generic errors by simply adding lots and lots of Calc measure to do comparisons and check conditions but than you swap a one simple generic error thats more of a notice than an error into a process that is:
A. More code thats not really that relevant.
B. Potentially add more stuff that can brake.
C. Potentially add to the process hogging.
Secondly, some errors are same like the notice of it being refreshed or whatever.
Thirdly, even multi billion companies have their software that get errors.
The difference, im a noob / the errors are accessible to users who dont know what to do with it most of the times / for nitpickers or people with OCD or what ever its called. xD
Lastly, what is it with you and the vColorRGBA? I suggest you take a look 10 more times, maybe youll get it. xD
Ill try explain simply (imagine some random skin being Skin XXX):
vColorRGBA can have whatever the hell value on its own. Its not important for Color Menu itself, its for the other skins.
vColorRGBA is a variable that is being set by external skins.
External skin sets vColorRGBA to a name that will be used as a variable name later in the Colors.inc.
So Skin XXX has background element and uses vBlah variable to set its color located in its Color.inc.
When you click an element that is meant to be recolored (like the background), Skin XXX sets vColorRGBA variable to vBlah.
Now, when you click apply in Color Menu, it will read vColorRGBA as vBlah and save a new color in the Skin XXX Color.inc as vBlah and not vColorRGBA.
That is the only instance vColorRGBA is used and is only for other skins. If you use Color Menu without actually using any skin for it, it will simply save whatever the default value of vColorRGBA is in Color Menu Color.inc instead.
So i actually purposefully set it to its own name as an easy way to check and debug it.
Its thanks to that that after all these years, when i went back to edit it, i instantly knew what the hell that last entry was in Color Menu Color.inc. xD
Get it?
Honestly, i was smarter back than. I dont use that trick so much anymore. xD
Than i get to an old skin to change, modify or upgrade and have no clue whats what, have to pathfind every element what its doing and why etc. Fun times.
But i digress...
The side effect of this approach is that every time Skin XXX clicks on an element that can be recolored and Color Menu is not running, an error will be logged because Skin XXX is trying to set a variable while the target skin isnt loaded.
Cant get around that.
So whatever you think you might know about vColorRGBA, you dont. Stop thinking about it! It will make you insane! :P

xD
Also, the skin is very old. Im trying to fix it by remembering the ins and outs of it how i wrote it back than. Need time.
Also, not a pro. Also also, where do you see those "syntax errors" and are you actually referring to actual errors from rainmeter or some syntax addon for notepad++ that went fubar? xD
Thanks for the mouse plugin tho, will play around with it.
Dont know what else to tell you. Everything works peachy on my end.
