I think some of you misunderstood what i ment about sharing scripts....
I realizing most public shard, especially big ones, will likely not share their scripts, and thats fine by me. I know there is some stuff I wouldn't share if I ran a shard, i want to be the ONLY place you can find it, i respect that.
But, I would rather the choice be this cut and dry, either you share your scripts so everyone can see how they work and do whatever you want with them, or you don't share them at all. Allowing compiled dlls gives a 3rd option, share the dll so people can use it as you have it (and no other way). I'd rather them not be shared than be shared in a DLL.
And yes, i'm aware an uncompiled script is just as dangeous as a compiled DLL, but anyone can look in an uncompiled cs file, and its not hard to see something obviously out of place. Not ever many scripts run threads, processes, open ports, or open files (let alone system files). If the person reading the script is unsure about it's security, they can always learn enough C# to find out, or ask someone else.
With a compiled DLL, these options aren't avaliable. There's no way for you to know whats really going on.
If an uncompiled script harms your machine, I consider it to be more your fault than mine. There's a whole community here, many of which know C#, along with 'the devs' who could easily be asked about potential script backdoors, if you don't want to ask them, thats your problem.
but if RunUO allows compiled DLLs, and you get harmed, I consider it my fault and not yours, although you should be more careful, other than just not using the dll,t heres nothing more you can do.
But for those who are wordering, the change required to allow precompiled DLLs is like 3 or so lines in the core. So it's not like it's hard to imnpliment, it's just a question of whether it's what we want.