Hey
@lfe, I know this plugin is pretty old, but I've discovered an issue with it that is problematic for the particular way that I am using it.
If you put the Light Texture plugin inside of a subscene, and then package the scene, with the subscene, and package custom textures that I'm using in the plugin in the same package, then the path SELF:/Custom/Atom/LightTextures/.. Will always only point towards the local custom folder and never the var that the textures were packaged in (along with the subscene and plugin).
I'm sure you have tons of free time just waiting to fix edge cases that users like me to discover issues with your five year old plugins.
Great mod though, allows a lot of interesting possibilites.
EDIT - I just noticed that two posts up, supperGR is having the same issue as me. Also, after further investigation, I actually don't think it has anything to do with the subscene, the plugin just can't seem to load textures from any .var file I put them in. So with the path being either var.LATEST:/Custom... or SELF:/Custom it never seems to be able to find the file. If the texture is located locally in Custom (not var), then it will use that instead, but this prevents being able to publish this as a resource. There are some workarounds, like I can set a loaddelay trigger to assign the correct texture, but I'm sure that's now how you intend it to work.