Executing code outside of .teaa in an addon: feature or bug?
Posted: Fri Mar 15, 2013 6:03 pm
So, I started adding a feature to an add-on I wrote that would allow people to run custom code (and in the process discovered that I'd basically done that already, just hadn't made it obvious, lol). The custom code, as I handle it, is just read from a file in the settings directory.
This is for the fx4fx addon (link in sig below) and I want to make it easy for people to experiment with making custom visual effects.
The drawback: letting people run custom code opens the path for all kind of cheats making their way on to the character vault. There may be other drawbacks I haven't considered as well.
Why I want to do it anyways: there are a lot of people who don't realize that they can code, even though they can. Eliminating the (admittedly minor) hurdles of unpacking the .teaa and breaking validation might lead a few people to experiment.
Any recommended policy regarding this? Anybody have any insight on why this would be a good or bad idea?
This is for the fx4fx addon (link in sig below) and I want to make it easy for people to experiment with making custom visual effects.
The drawback: letting people run custom code opens the path for all kind of cheats making their way on to the character vault. There may be other drawbacks I haven't considered as well.
Why I want to do it anyways: there are a lot of people who don't realize that they can code, even though they can. Eliminating the (admittedly minor) hurdles of unpacking the .teaa and breaking validation might lead a few people to experiment.
Any recommended policy regarding this? Anybody have any insight on why this would be a good or bad idea?