Stop asking if Oxide can run Fougerite plugins. It never will.
As for the new people, you might have noticed the Plugin's Engine at the resource. If not, I attached a picture for this post. The reason of this, because Fougerite supports several languages. So what do they mean?
Programming Language Speed Test
Currently we have four engines:
- Jint (Magma Plugin) - This is the old engine of magma, which is Jint 1. This means It's even compatible with magma. Unless It uses some new methods that are not available in Magma. The plugins that run on It must be copied to the Magma folder under Save.
- Jint2 (Jint) - Not many people use the new Jint engine. The only difference between the old and the new one is that the new one is faster. The plugins that run on It must be copied to the JsPlugins folder under Save.
- Python (IronPython) - More people used It on Fougerite in order to create much faster plugins, and It also fits people who didn't want to use a C# compiler. Python fits people's need just like Jint, the only difference is the language syntax, and the speed. Python is the second fastest engine available to the Plugin Developers. The plugins that run on It must be copied to the PyPlugins folder under Save.
- C# Modules. (DLL FILES) - The fastest engine that is available, since Rust is written in C#, the C# plugins are just way too faster than all the other 4. The "suffering" with an IDE is worth if the developer wants to create huge plugins, or just to create a plugin which needs more CPU or RAM, or the developer can prognosticate that the server will probably lagg on Py/Js/Lua. The plugins that run on It must be written in the Fougerite.cfg. Read more at: http://fougerite.com/posts/3770/
- Lua (MoonSharp) - The new engine for Lua plugins. This engine is 99% compatible with Lua 5.2, and currently has the same hooks/methods as the other engines. I plan on adding Oxide plugin compatibility to It. The plugins that run on It must be copied to the LuaPlugins folder under Save.
24.3 KB Views: 298