1. Tuntenfisch submitted a new resource:

    RemoveAAA - Item command permissions and admin abuse announcement removal

    Read more about this resource...
     
  2. Yes, lets help the server admins cheat again.
     
  3. well it does not work when I put this in grant ownerid 76561197988847132 removeaaa.give
     
  4. Tuntenfisch updated RemoveAAA with a new update entry:

    0.2


    [DOUBLEPOST=1453596343][/DOUBLEPOST]
    Take a look at the overview section, the usage is explained there.
    [DOUBLEPOST=1453596398][/DOUBLEPOST]
    I'm not trying to encourage admin abuse.
     
  5. Code:
    [Oxide] 2:23 AM [Warning] Calling hook OnRunCommand resulted in a conflict between the following plugins: rustcore, RemoveAAA
    I know, it's only a warning and I can imagine why it's displayed, but its annoying anyway ;)
     
  6. v3x

    v3x

    On my server I'm the only one that can give stuff, but I only give myself stuff to either test something or make a kit, then I throw it in the ocean. Now I don't have to announce it to everyone in chat what I'm doing. Thank you for this plugin. +1 like
     
  7. Implying people weren't already just using the /give command. Adding the announcement was stupid, no matter how regular players see it.
     
  8. I am an admin and also very new to it. So I have to test a lot of things. Also I often build community structures, and sometimes not with the build plugin, so it was just annoying if i gave myself 15000 wood and spammed the chat with it.
    Moderators will not have this ability.
    So I can't see the problem.
    Thank you for this option/plugin Tuntenfisch
     
  9. That's odd, That warning only pops up on the latest oxide version. It didn't pop up on the version before that. I'm not actually sure if I can even do something about it but I'll look into it.
     
  10. Wulf

    Wulf Community Admin

    The conflict warnings have been in there for a year or so, they will happen when you try to override a hook. The core extension for Rust uses it, which is what is shown in the example above.
     
  11. So basically it sometimes happens that the core extension and my plugin return a different object within the same hook call which obviously results in a conflict. How would I go about avoiding this?
     
  12. Wulf

    Wulf Community Admin

    There isn't any way to avoid it when you're overriding default command handling as far as I know.
     
  13. That's what I thought, as well! I actually looked at Oxide.Core.Plugins.PluginManager.CallHook(...) which I think is responsible for highlighting conflicts and I was kind of confused by this at first:
    Code:
    string[] name = new string[num];
    int num1 = 0;
    for (int j = 0; j < plugins.Count; j++)
    {
        if (objArray[j] != null && objArray[j] != obj)
        {
            int num2 = num1;
            num1 = num2 + 1;
            name[num2] = plugins[j].Name;
        }
    }
    Isn't that basically the same as:
    Code:
    string[] name = new string[num];
    int num1 = 0;
    for (int j = 0; j < plugins.Count; j++)
    {
        if (objArray[j] != null && objArray[j] != obj)
        {
            name[num1] = plugins[j].Name;
            num1++;
        }
    }
    I'm really not trying to criticize the code here, I was just looking at it to see how conflicts are highlighted and kind of struggled with this part at first.
     
  14. Wulf

    Wulf Community Admin

    Probably, there's a good bit of older code that hasn't been touched since it was written.
     
  15. It's fairly simple, Admins/Owners own the server. If they are giving friends supplies and resources to help them against other players then that is crappy but if they choose to give themselves resources for whatever reason and people don't like it, there are plenty of other servers out there.

    This.

    I tried this and many other different wordings, it doesn't work for me either. It is a great plugin and hope it all gets sorted.
     
  16. What about: grant user 76561197988847132 removeaaa.give
     
  17. This messaging was added because of rampant abuse by server admins. Due to the voting it is obvious the majority want this to stay and by you bypassing it makes you and the people that use this look like cheaters. If the vote stays in the favor of leaving it, I hope they remove this plugin and disable the ability to do this.
     
  18. Fine by me, I was just making it because I like to code. :)
     
  19. And you continue to fail to realize that the majority of people who want it gone are regular players who have no idea what non-abusive things it can be used for.

    Once again, restricting our ability to modify things in the game does nothing, because there's always a way around. For example, no one has to use the F1 menu. If they're using Oxide, they can just use the /give plugin, pretty simple, really.
     
  20. HIGHLY Unlikely that this mod will be removed if the vote passes to keep the messages:

    If you read the latest dev blog (94) there are a few key things said to note:

    A lot has been written over the last week about the admin spawn announcements. We added these announcements so that the members of the server are aware when an admin is spawning items. We feel that a large wedge of the server admin community owned a server so they could basically use it as a sandbox. While this is fine (It’s their server, their money), we feel that the members of the server need to be aware of this. If a group of people on a server are spawning whatever items they need instead of playing the game, it’s no longer a vanilla game, and The server should be on the modded tab.