CommandBlock

Moved

Total Downloads: 985 - First Release: Oct 15, 2014 - Last Update: Aug 30, 2017

5/5, 7 likes
  1. Wulf

    Wulf Community Admin

    The real command is "global.grant" else you can use "oxide.grant", "global." is just assumed by Rust if none is given.

    For the inventory one, it should block it unless you have another plugin handling it such as Admin Spawn or RemoveAAA.
     
  2. Wulf I am with oxide version : (09:11:10) | [Oxide] 09:11 [Info] Oxide 2.0.2031 for Rust 911.49 (1379)

    And I see this message :

    (09:01:02) | [Oxide] 09:00 [Warning] 'commandblock v0.2.3' is using deprecated hook 'OnRunCommand', which will stop working on Monday, 01 August 2016. Please ask the author to update to 'OnServerCommand'
     
  3. Wulf

    Wulf Community Admin

    That's just a warning, shouldn't affect its usage.
     
  4. Not working for me..
     
  5. It´s not working Wulf. :)
     
  6. Wulf

    Wulf Community Admin

    Update Oxide.

    What exactly isn't working? Should be working fine on any of the last few Oxide released builds.
     
  7. I´m trying to block kill command, but everybody can use it.
     
  8. Wulf

    Wulf Community Admin

    global.kill is like what you'd need to add. There are plugins that handle this too such as LimitedSuicide for Rust | Oxide.
     
  9. I´ll try.
    LimitedSuicide doesn´t works for me.
     
  10. Wulf

    Wulf Community Admin

    I have another too I'll be posting soon called NoSuicide most likely, might take over LimitedSuicide and merge.
     
  11. Oh, okay.
    I tested all the plugins that blocks commands and i can´t block kill...
    Why?
     
  12. Wulf

    Wulf Community Admin

    Could you upload your config for me to see please?
     
  13. I tested it with:
    Code:
    {
      "Messages": {
        "Blocked": "No puedes usar ese comando."
      },
      "Settings": {
        "AuthLevel": 2,
        "ChatName": "APHAROS",
        "Commands": [
          "global.kill"
        ]
      }
    }
    and:
    Code:
    {
      "Messages": {
        "Blocked": "No puedes usar ese comando."
      },
      "Settings": {
        "AuthLevel": 2,
        "ChatName": "APHAROS",
        "Commands": [
          "kill"
        ]
      }
    }
     
  14. Wulf

    Wulf Community Admin

    global.kill would be it, but here's ya go:
     

    Attached Files:

  15. It works!!

    Thanks Wulf.
     
  16. Wulf,
    is there an option for me to block anybody with authlevel 1 or lower to not be able to use the noclip command? When I enter nolclip as a blocked command, it doesn't appear to disable the command.
    Code:
    {
      "Settings": {
        "ChatName": "SERVER",
        "Commands": [
          "noclip",
          "server.seed"
        ]
      },
      "Messages": {
        "CommandBlocked": "Sorry, that command is blocked!"
      }
    }
     
  17. Wulf

    Wulf Community Admin

    The "noclip" in Rust is not a command, it's a client-side only setting that never gets sent to the server.
     
  18. that would explain why it isn't working for me. do you know of a solution to accomplish this? I basically want to prevent anybody authlevel 1 or less to not be able to use the noclip command.
     
  19. Wulf

    Wulf Community Admin

    The only way you'd be able to is by not giving them any auth level.
     
  20. do you know if it is possible to write a mod that would affect the client side preventing use of that command without the appropriate auth level? or a way to create an oxide group that can spawn items and use "maybe" some selective server side commands?(like changing time of day?)