Fix "Could not load plugin 'name' (no plugin found with that file name)" in Oxide

oxide.load and oxide.unload take the plugin file name, not the title from the [Info] attribute, and the lookup is a plain string match on the file's base name. On Windows and in the default case-insensitive filesystem setups, oxide.load KillRewards finds killrewards.cs, but on a Linux host running a case-sensitive ext4 volume it does not, and you get this message. The loader also only scans files ending in .cs; a plugin downloaded as KillRewards.cs.txt (browsers and editors often append an extension, and some panels hide known extensions) sits in the folder but is never seen, so loading by the name you see in the file list fails too. The same message appears when the file was removed, renamed, or never uploaded, and when you are pointed at the wrong directory — oxide/plugins on Oxide, carbon/plugins on Carbon. Note this is a name/file lookup error, not a compile error: nothing has been compiled at this point.

1. List the plugin folder and compare names exactly: ls oxide/plugins. On Carbon use ls carbon/plugins.
2. Load using the file base name exactly as shown, without .cs: oxide.load killrewards if the file is killrewards.cs.
3. If the suffix is not .cs (for example .cs.txt), rename the file to <Name>.cs and remove the extra extension.
4. If the class name inside the file does not match the file name, rename the file (or the class) so both are identical; Oxide reports this separately but fixing it now saves a second reload.
5. Confirm with oxide.plugins — the plugin should now appear. A successful first load prints Loaded plugin <Title> v<Version> by <Author>. Compile errors would print Error while compiling <Name>: instead, which means the load call itself worked.