Oxide Development and Community Update

You might already know, but the Oxide team is planning on making improvements to the Oxide framework, the website, and other related tools.


 The Sandbox

The first thing we plan on doing is removing the sandbox. The inclusion of the sandbox has been a controversial topic for many years. Nowadays, hosts use containers to separate clients on shared machines and as a result, the sandbox has become obsolete. It has become more of a limitation for developers than it is a safeguard for server owners, so starting with next force wipe (April 6th), the sandbox will be completely removed.


With this change will come a revision to our plugin submission guidelines. We will now be allowing plugins using reflection and harmony. The site will be updated to reflect this.


If you have and questions or concerns about the removal of the sandbox (or any other changes or matters) please reach out to any member of the Oxide team.


 Oxide Framework

We have been working on replacing our ancient Mono compiler with the more modern Roslyn compiler which will support newer C# versions and features.

Additionally, we are working on upgrading our tools and the framework to support runtime patching for hooks. This means that instead of using our patching tool to inject static method calls into the server files, then distributing those modified files, Oxide will be able to dynamically patch and un-patch those method calls as and when they are needed.


The main benefits of this are:
- A reduction in the number of unnecessary hook calls, resulting in a performance gain.
- No more dragging and dropping oxide files into your managed folder each update.
- Out of date hooks will just not patch instead of (possibly) causing unexpected behaviour.


We are close to completing these new features and internal testing will be happening throughout this month, with hopefully a public test build being released soon.


 Help Wanted

We are a small team, always looking for another pair of hands. We are looking for people to fill these roles:

- Core Developers => Maintain and develop the core Oxide framework, either fixing bugs or implementing new features.

- Plugin Reviewer => Curate plugin submissions on the website, ensuring plugins follow the guidelines and have a base level of code quality.

- Documentation => Write helpful documentation about the Oxide framework (hooks, libraries etc.) or how to use it (installation, commands etc.).

- Web Developers => Someone capable of developing websites or creating designs (or both!).


If any of these roles interest you, please send a message to an Oxide team admin.



We now have a platform to receive your feedback and suggestions.

Note: This is for feedback related to the framework, website, or other related things, not for hook requests. We are working on a separate form to request hook additions.



To keep up with updates, new releases, and ongoing developments join our discord server:


This is fantastic news. These changes will bring a lot of positive impact on the community. Keep up the good work!

Expired Discord link


Expired Discord link

Lol Umod wont let me post there discord link but here it is remove the spaces.
Or look at the bottum of this page under the Help Section for the link.
Or at the top of the page.

discord.     gg/oxide

VVw12TJj7fpv9ON.png Razor

Lol Umod wont let me post there discord link but here it is remove the spaces.
Or look at the bottum of this page under the Help Section for the link.
Or at the top of the page.

discord.     gg/oxide

I completely understood what you were talking about. thx


Expired Discord link

Should be fixed now, thanks.

Please Fix for hurtworld-

Could not check for update to Compiler.exe

Wish you guys would consider PalWorld for the next Oxide game.

Literally the best plugins & mods EVER have all come from Oxide based plugins.

And god damn that game really needs decent modders compared to what is there now.