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.
CommandBlock
Moved
Total Downloads: 985 - First Release: Oct 15, 2014 - Last Update: Aug 30, 2017
- 5/5, 7 likes
-
Wulf Community Admin
-
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' -
Wulf Community Admin
-
Not working for me..
-
It´s not working Wulf.
-
Wulf Community Admin
-
I´m trying to block kill command, but everybody can use it.
-
Wulf Community Admin
-
LimitedSuicide doesn´t works for me. -
Wulf Community Admin
-
I tested all the plugins that blocks commands and i can´t block kill...
Why? -
Wulf Community Admin
-
I tested it with:
Code:{ "Messages": { "Blocked": "No puedes usar ese comando." }, "Settings": { "AuthLevel": 2, "ChatName": "APHAROS", "Commands": [ "global.kill" ] } }
Code:{ "Messages": { "Blocked": "No puedes usar ese comando." }, "Settings": { "AuthLevel": 2, "ChatName": "APHAROS", "Commands": [ "kill" ] } }
-
Wulf Community Admin
Attached Files:
-
-
Thanks Wulf. -
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!" } }
-
Wulf Community Admin
-
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.
-
Wulf Community Admin
-