Update compiler so you can use the latest C# version Allow namespace oxide.plugins.{PLUGIN} Allow multiple .cs files in a .zip file (can be special extension like .cszip)

The ability to be able to define what kind of logs are relevant per log destination (console, file) Levels should include: Debug Chat Information Warning Error Stack trace

Remove the requirement to log in to see the works with + used by section. Most people don't even sign in as it's not required to download plugins. Or require sign in to download? IDK /shrug

It would be great to be able to see the RAM usage of each plugin when using the o.plugins command to make identifying poorly written plugins easier.

Enhanced PluginReferenceAttribute Proposal I propose refining the PluginReferenceAttribute by extending its functionalities in the following ways: ### 1. Introducing Minimum Version Requirement: - Functionality: * Allow the sp

The consensus is, the sandbox feature should be retired as not only does it not offer any actual security, but also imposes artificial limitations on *.cs plugins

Hooks should be able to convert things like BasePlayer to IPlayer or vise versa and other types using a conversion interface.

hello could you add a hook to control the flares of the patrol helicopter when it is attacked by players from the Homing Missile Launcher? thanks a lot

Doesnt have to be through sentry but access to veiw errors of your plugins for any plugin author

Spin up servers on azure to test all public plugins for each update. Support ability to test plugins outside ecosystem for a fee. Provide hooks that allows you to run more detailed tests in your plugin if you desire.

Would be cool to have a config file like oxide.config where all the hooks will be listed and we could tweak with true/false which we want to be subscribed on server start, something like: "hookName", true "otherHookName", false Theres probably a b

Language folder is not the main language Language - plugin name.json -> Plugin name - en.json, ko.json, es.json (If there is no language.json file, I think it would be okay to read the default en.json file!) I think it would be easier to man