An Oxide plugin consists of a single .cs, .js, .lua, or .js file. To install the plugin on your server, your server provider must support Oxide 2 - else the plugins won't do anything. If you are self-hosting, make sure you already have Oxide 2 installed. Download a copy of the plugin you wish to install. They can be found in the Plugins section. Make sure to not rename the plugins. If you aren't hosting locally, connect to your server via an FTP client. If you are unsure of your FTP details, pleas contact your host. Locate the "plugins" folder, normally located at server/my_server_identity/oxide/plugins, but may changed based on your +server.hostname setting. If you can't find it, you may need to install Oxide 2 still. If you already have, make sure your server has been launched at least once. Upload the plugin file (.cs, .js, .lua, .py) into the "plugins" folder and it will be loaded automatically. Configure the plugin by editing the matching named .json file, normally located at server/my_server_identity/oxide/config. If you don't see any configuration file for the plugin, then it either does not have one or the plugin did not load successfully. Reload the plugin if you edited the config using the "oxide.reload pluginname" console command. If a plugin isn't loaded automatically, ensure your server provider supports Oxide and that Oxide is installed on your server. You can also check for errors under the logs folder. Some plugins store persistent data. This data can be found and reset in the "data" folder (this should exist alongside the "plugins" folder). The data files are sensibly named. Deleting a data file will reset it (so deleting the data file for Door Sharing will reset all share lists). This can be useful when performing a server wipe.