So what am I on about this time, right?

Well, the RustEssentialsAPI.
That's right. It exists now.

...Well partially.

It is very barebone. The security in it is barely setup and there aren't any hooks or event handlers. The only things it can do is anything the base mod does, which actually is a lot.

I have implemented 3 programming languages - C#, VB, and JScript .NET (very similar to JavaScript). What I need from you guys is to help me come up with possible security flaws (such as giving people the ability to create and read files with System.IO - this is bad because they can create malicious files or read things they shouldn't) and good hooks/event handlers to implement for the API.

Now let's pretend this is the fight club. You know about the fight club. No one else knows about the fight club. If someone asks about the fight club, you don't say anything. Don't talk about fight club.

Since this stuff is at such an early stage, I won't be releasing it in 1.8.0. The mod is very dynamic when working with the API/script compiler. The API is actually a separate mod from the base mod, and the base mod can run without the API's DLL installed. This way I can release updates for the base mod without having to re-release the API every time. Right now, the API compiles the 3 languages of scripts using what is called CodeDOM and, because of Unity, is compiled in a separate process (through a C# Console Prompt I made called compiler.exe). After the scripts are compiled into DLL's, they are loaded into the RustEssentialsAPI. The problem with the current way I'm doing it is that instead of just executing the scripts directly, I'm compiling them into what are called assemblies and loading them. The problem with THAT is that when you load an assembly, you can't unload it. Which means at the moment, you have to restart your server to reload plugins. But hey, I can figure something out sometime later.

So, yea. I'm terrible at ending announcements.
Soooo Boom.