When I set the skin to "custom" and start making new skin, something strange happens that goes away once I make a compiled skin.
When I create variation files, 2.txt, 3.txt etc, certain things won't read properly from the variation files. Example, when I set a different bitmap value inside 2.txt it doesn't always read it and make the change.
I have discovered a way to fix this during development of a skin by placing an OPTION WTF="Keep me checked for now!",1 at the bottom of the options list. Then at the bottom of all files I place [WTF] and this forces all options to be read.
Once I create a skin file I can remove all of this and it works correctly. Only when a skin is being read in custom mode do I have to do this.
It did it in 3.5 and in 3.6 so I figured I should report it. I was wondering why there is not much skin support for this awesome program. I am starting to think that anyone who ran into this trouble that was not able to figure out a work around gave up on making skins. I think if you fix this you might find out there are more people out there trying to make skins then we all realize.
Log in to post a comment.