The Rust oxide location is still hard coded.

Hi, I actually replied to the closed support request saying this is still a problem, but clearly this site doesn't flag that up to you as a reply. Oh well.

I'm still having the same error message rendering the plugin unusable for me. You can see below that the path to the config json is hardcoded (or it's assuming that the oxide directory is directly under the \Rust\ directory) so the plugin is failing to load. However I use the method where the server locations are set in a sub-directory at \Rust\server\ and the oxide directory is in a sub-directory of each server so that all my servers are together and I only need a single installation of Rust to run them all (saving ~6GB to 8GB of storage for each additional server, and I have 4 altogether with a 5th on the way), done like this under Windows:-

RustDedicated.exe -batchmode -nographics -logfile output_log.txt ^
+server.identity "PvPTEST" ^
+oxide.directory "\server\{server.identity}\oxide" ^

You fixed the same issue for StaticDispensers, would you please fix it for this plugin? I purchased it at the beginning of April and you were going to fix it in the next version, but obviously you didn't as that version has come and gone.

¯\_(ツ)_/¯

-PPlank

Quote

Failed to initialize plugin 'aMAZEingPro v2.9.2' (Exception: Only access to oxide directory! Path: C:\GameServers\Rust\oxide\config\aMAZEing.json) at Oxide.Core.Configuration.DynamicConfigFile.CheckPath (System.String filename) [0x00029] in <c2afd8354b8b4f3ca451cf5a1aa111c3>:0 at Oxide.Core.Configuration.DynamicConfigFile.Exists (System.String filename) [0x0000c] in <c2afd8354b8b4f3ca451cf5a1aa111c3>:0 at Oxide.Plugins.aMAZEingPro.Loaded () [0x00032] in <49512081cb37457788fe980672a517c2>:0 at Oxide.Plugins.aMAZEingPro.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x003ff] in <49512081cb37457788fe980672a517c2>:0 at Oxide.Plugins.CSharpPlugin.InvokeMethod (Oxide.Core.Plugins.HookMethod method, System.Object[] args) [0x00079] in <3606d2af539c45e4b5c61658e6a8b307>:0 at Oxide.Core.Plugins.CSPlugin.OnCallHook (System.String name, System.Object[] args) [0x000d8] in <c2afd8354b8b4f3ca451cf5a1aa111c3>:0 at Oxide.Plugins.CSharpPlugin.HandleAddedToManager (Oxide.Core.Plugins.PluginManager manager) [0x0006e] in <3606d2af539c45e4b5c61658e6a8b307>:0

So are you going to fix this then? It's been several weeks (April 4th was my first report of this bug) with a promise of a fix in the previous update, which as we know didn't happen. The plugin is currently unusable for me. If you don't want to fix it, I'm perfectly fine with that, just refund me and I'll be on my way like a good little PPlank.