installation-and-configuration/Permissions
Permissions
Three systems are supported by HawkEye for permissions:
- Any permissions plugin supported by Vault (if you have it installed)
- PermissionsEx
- Permissions (both v2.7 and v3.*)
- BukkitPerms
Nodes
Any of those three can use the following nodes:
Node | Function |
---|---|
hawkeye.* | Access to all HawkEye commands |
hawkeye.page | Permission to view different pages |
hawkeye.search | Permission to search the HawkEye database\ |
hawkeye.search.<action> | Permission to view specified action. Use HawkEye.search.* to give access to all actions. Use negative permissions to deny viewing of actions e.g. -HawkEye.search.command |
hawkeye.tpto | Permission to teleport to the location of a search result |
hawkeye.rollback | Permission to rollback actions |
hawkeye.tool | Permission to use the HawkEye tool |
hawkeye.tool.bind | Permission to bind parameters to the tool |
hawkeye.preview | Permission to preview a rollback before applying it |
hawkeye.rebuild | Permission to rebuild actions |
I'm using PermissionsEx
but my players can still use the commands:
/he, /hawk or /hawkeye commands
can you fix it so they'll not be able to see the command list? Thanks
I am admin on my server using Bukkitperms (PermissionsBukkit) with the permission hawkeye.*: true, but I cannot search any actions because of lack of permissions.
@Drat333
bukkitperms doesnt support the wildcard node, the *. you need to add each node individualy
@Drat333
HawkEye does not seem to support PermissionsBukkit at all. Give yourself OP status and it should work fine.
@azurefoxfire
PermissionsBukkit supports wildcard nodes specified by individual plugins. For example, commandbook.* gives me access to all of CommandBook's permissions.
On the other hand, looking at my console upon startup, I can see that HawkEye is not recognizing PermissionsBukkit as a permisssion handler via the statement:
The permissions nodes are now working. Hopefully you can fix!
@TheGurw
It does appear to support SuperPerms. Even though it claims it is operator only it still checks to see if the player has the permission as normal using SuperPerms.
As long as you have assigned the permissions through PermissionsBukkit it should work fine.
Could you please werollback nodes for use by GM?
This indeed looks like a very useful tool! Great work!
I'll have to test this on a clean craftbukkit install, but it appears that by default the /hawk command is accessible to all players. At the moment I am using only PermissionsBukkit, which I realize is not supported by this plugin, with a strict whitelist-only policy (all grant, no deny), so usually I do not expect to be able to execute commands before explicitly granting myself access. My handle is not in the ops.txt file. Is a compatible permissions plugin supposed to be required to deny access to non-ops?
@falkensmaze
Further testing with no other plugins installed reveals that while access to the /hawk command by itself (harmlessly displays help) is allowed to non-ops, the subcommands are not by default, so it is not quite the security issue as I had assumed. Still, I would prefer to see the usual "You do not have permission to access that command." when I am testing group abilities. Also, the /help command from Essentials uses permissions to determine which commands to display, so ideally /hawk would not show up for those not authorized to use it.
Hello, I want some of my players give permission to hawk tool, but they don't have access to /hawk page to list through pages. How should I do this? hawkeye.search.page is not right permission and i don't want them give full hawkeye.search.
Is there any way, how to give permission for players only to use /hawk tool and list through pages with /hawk page?
I have Vault - 1.2.8 and bPermissions - 2.1.4b yet when HawkEye starts it says no permissions handler found so only ops can use it. Help PLS!
@ASWeiler You sir should read which permissions are compatible with Hawkeye therefore you shouldn't have a problem with this plugin. Permissions 2.7 and v3.*, Bukkit Permissions, and PermissionsEX are compatible with this plugin
@NovaCreator
PermissionsEx uses Bukkit's permissions (superperms), so does bPermissions and PermissionsBukkit, so they are all compatible with HawkEye.
Old Permissions 2.7 and 3x should never be used anymore, by anyone, at all. If they are still working then you are lucky, but they are outdated and unsupported by Bukkit, and it's a wonder that HawkEye even makes the attempt. Are people still playing Beta 1.3 or something?
Vault should not interfere with this - bPermissions uses superperms and therefore should be compatible.
Is it possible to set /he tool so that it takes away the block/item once you type the command again? I want to give this to my users but not give them a free log block in the process.
@CombatWiZ
You could always use an item that does nothing, for example "383".
It doesn't stack, and can't do anything what so ever.
It would clog a users inventory if they tried to spam the command.
If you use Essentials, you may wish to charge a very small sum (1 coin) to use the command, and this would deter anyone from massively spamming the command as well :)
I gave my self all of the permissions (hawkeye.*) and i reloaded permissions ex, and it still wont work here is my permissions file
groups: Brony: default: true info: prefix: Brony default: true permissions: - jcommands.back - jcommands.back.ondeath - jcommands.boom - jcommands.nuke - jcommands.day - jcommands.night - jcommands.gamemode - jcommands.home - jcommands.sethome - jcommands.smite - jcommands.spawn - jcommands.tp - jcommands.tphere - simplespleef.help - simplespleef.announce - simplespleef.join - simplespleef.arenas - simplespleef.ready - simplespleef.start prefix: '&b(Brony)' Admin: info: prefix: Admin permissions: - '*' - multiverse.portal.access.8b - hawkeye.* prefix: '&c(Admin)' Owner: info: prefix: Owner permissions: - '*' - multiverse.portal.access.8b - hawkeye.* prefix: '&5(Owner)' users: mdo13: group: - Owner ChalkleyB: group: - Admin philipb357: group: - Brony users: mdo13: group: - Owner philipb357: group: - Brony group: {}
Any Idea??
sorry about formatting... here is pastebin:
http://pastebin.com/Wc9HNYvA
Is anyone else having problems with giving a group (using Essentials' GroupManager) hawkeye.*, and then not being able to search actions?
Giving individual permissions such as hawkeye.search.block-break, but not hawkeye.search.* Edit: for those curious, I've got Vault installed.
@Westy543
Yes, my server is also running GroupManager and having the problem.
@Westy543
@BallisticKat
If you pay attention to the post, you see that HawkEye only supports
-Any permissions plugin supported by Vault (if you have it installed)
-PermissionsEx
-Permissions (both v2.7 and v3.*)
-BukkitPerms