Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

PPlank

Member
  • Posts

    28
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

PPlank's Achievements

Contributor

Contributor (5/14)

  • Week One Done
  • One Month Later
  • First Post
  • Collaborator
  • Conversation Starter

Recent Badges

7

Reputation

  1. PPlank

    Exclusion

    Add console commands. Then it could be used to create a paid access Build server using for example Crafting Store.
  2. 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.
  3. PPlank

    A bug and a question

    A question first. How do I move the button? It's smack bang on top of the BackPacks icon. I've tried changing all the x, y values in the config with no success. I'd like it moved to the opposite end of the normal hotbar. The bug I've discovered is that it jumbles the items around when you add them to a hotbar, so that when you select them you then have to move them into their original positions. This is very irritating for people with mild OCD like myself.
  4. PPlank

    Hotbars

    So you mean perms like this? hotbars.use.1 hotbars.use.2 hotbars.use.3 hotbars.use.4 hotbars.use.5 That would be good. I'm just about to get it anyway as I don't think I need that functionality, and then make it a lifetime perk on my servers for a few dollars. Update: Got it. And, yes I do need that perms functionality from above. My plan is (probably) to give everyone a single swappable hotbar so that all can see it, and then create lifetime perks for 3 and 5 hotbars. So, if you could also add an option to show the other hotbars, but greyed out /unaccessible that would be perfect as the default users would then see that more could be available.
  5. I've sent you a friend request on Discord. Name of PPlank. Aaaaand I just realised there's a Codefling Discord, so I've joined that too.
  6. 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
  7. PPlank

    Quarry Levels

    Well that's great for you but it doesn't help me at all. I also use BackPumpjack and none of the config options in that plugin affect access to Quarries and Pumpjacks. I bought this plugin (I believe) on the day it was released (maybe the day after) and I'm suspicious that the later version works quite differently to the initial one and may have changed the quarries and pumpjacks in some way that is preventing owners (and me as admin) from accessing quarries and pumpjacks on any of my servers. You'll notice that there's no v1.0.2 and that's because it was removed after it broke all the existing quarries. I had to give players new quarries and told them to destroy their old ones. They were not happy. I was hoping that v1.0.3 would resolve the problem but it seems to have introduced a new one. For now, the stopgap that is working for me is reverting back to v1.0.1 and using QuarryLocker to protect the quarries and pumpjacks on the PvE servers amongst clans, friends and team members (authorised users), but I'd like to see a resolution to this issue that I and other server admins are experiencing, natively in this plugin.
  8. PPlank

    Quarry Levels

    I'm getting the same issue reported that owners can't turn on and off quarries any more - they definitely own the quarries. As admin I can't access them or turn them on or off, even when I set these to false:- "PreventUnauthorizedToggling": false, "PreventUnauthorizedLooting": false I've reverted back to v1.01 and all seems well, but 1.03 needs a bit of work. I've re-added the QuarryLocker plugin to protect the player quarries so I've got a solution that works until you can fix this problem. Other than this, great plugin and the players love it.
  9. PPlank

    Hard coded Rust location

    I'm still having the same problem. 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
  10. The only element on the page that looks like it might be a theme switcher is the little cog at the top of the page, but clicking it does nothing. I'd really like to view this site with the original light theme as I've seen one too many dark themes. (They suck.)
  11. PPlank

    Quarry Levels

    Yeah that would be a great addition.
  12. PPlank

    Console Chat

    It's a nice plugin, really good idea to be able to see all the text chat in the console. A couple of things though... 1) It needs a time adjust as it's picking up UTC time which is an hour behind the server time. 2) Any way a player can copy the text from the console? Other than those little things, great job, thank you.
  13. PPlank

    Hard coded Rust location

    Hi Raul-Sorin, I have the same problem I had with StaticDispensers where the plugin is looking for my \oxide\ directory directly under the \Rust\ directory. Thank you for fixing StaticDispensers, can you work your same magic on this one? Thanks. -PPlank "Failed to initialize plugin 'aMAZEingPro v2.9.1' (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 <9a0aabaddd5f4137afb427e4098a997d>:0 at Oxide.Plugins.aMAZEingPro.DirectCallHook (System.String name, System.Object& ret, System.Object[] args) [0x003c4] in <9a0aabaddd5f4137afb427e4098a997d>: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)"
  14. PPlank

    Hard coded Rust location?

    "Failed to initialize plugin 'StaticDispensers v1.1.0' (Exception: Only access to oxide directory! Path: C:\GameServers\Rust\oxide\config\StaticDispensers.json)" I just added StaticDispensers to my test server and it looks like 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, like this:- RustDedicated.exe -batchmode -nographics -logfile output_log.txt ^ +server.identity "PvPTEST" ^ +oxide.directory "\server\{server.identity}\oxide" ^ As you can see in the console output at the bottom of this request it looks like the plugin is assuming that all installations of Rust are in the default path, whereas I know server owners who use the same method as I do so that a single installation of Rust is used. (This makes it easier to update Rust at wipe time, edit server files, do backups and keep everything neat and tidy all from a single installation.) These two images show the directory structure of my single Rust installation, plus all the servers I run underneath it. And each server looks like this with \cfg\ and \oxide\ in the same place:- Full console output NRE:-

About Us

Codefling is a forward-thinking platform for developers to share and monetize their work from plugins to game assets and everything in-between.

4,304 files sold to 448 customers and $63,247 of payments processed this year!

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.