@ktross

Fantastic. I'll give it a try.

EDIT: The lead issue does appear to be fixed. Does this mean it may be possible to fix (allow) other interactions with naturally spawned horses such as taming, saddling, and mounting/dismounting?

My young son nearly came to tears when he accidentally mounted(*) the horse he had brought to his pen and it disappeared upon dismounting. ;-) (*This of course occurred because before this build I had to grant players the horsemount.mount command to allow them to even lead them.)

EDIT #2: It dawned on me that per your feature list ("Only let players mount horses if they have permission"), some server admins might want to restrict horse mounting only to players granted the horsemount /mount permission(s) the horsemount "way". So my thought was that if you were able to allow other interactions with naturally spawned horses, adding a config parameter like "disable-naturalhorse-mounting true" could disable mounting outside of using the horsemount /mount command (if granted the permissions). If set to false, players granted the horsemount.mount permission could use the /mount command for a quick mount and all players could interact with naturally spawned horses normally.

Sorry if I appear to be "pushing" my idea. That is not my intent. I just can't get my brain to stop once it starts processing a "problem". ;-)

@ktross

Any luck sorting out the lead issue? I am currently forced to give my users horsemount.mount and horsemount.dismount if they are to interact with naturally spawned horses at all. Thankfully, I can still block them from using /mount by not adding the style, color, etc. permissions but that isn't ideal.

Me again, this time with some feature requests/ideas. :-)

How about a /showmount command to show the current /setmount parameters? I know you could call /mount and look in inventory but that view is a little small and can be hard to tell with armor. My "justification" is similar to the current dismount setup- you can really just hit Lshift but the "/dismount" command is there if you prefer it.

Also, it would be helpful to the player if the order of the parameters for the /setmount command were listed in the help, like /setmount: Set your default mount to <variant> <style> <color>

@ktross

Ok, thanks for the quick update! My previous comment was actually composed while you were responding so I will check if the help part is still an issue. My other questions stand. ;-)

EDIT: Other than help as noted above, the permission nodes in 1.0.1-SNAPSHOT are working correctly now. Thanks!

@ktross

Also, I noted that horsemount.help permission isn't working. I tried adding a "-horsemount.help" in an attempt to force some players to leash/lead and mount horses the "normal" way by not showing them the /mount command but the help shows regardless. (Conversely, I also didn't need to add the permission for the help to appear so it's not working either way.)

Another question: If I don't grant the horse.mount permission I discovered players can't manually leash/lead a horse either. Would it be possible to separate the permissions to leash/lead a horse as opposed to actually trying to saddle & mount it? Or does Minecraft (/CraftBukkit) roll all of the horse interactions under "mounting"? (Looking at it another way, could the horsemount.mount command be limited to dealing with horses acquired via horsemount as opposed to "wild" horses?)

I am trying to allow some players to deal with horses the "traditional" way (or just be able to collect them before they actually find a saddle) while advanced users/ops can use the /mount command as shortcut.

Horses disappear when u hit water is that whats meant to happen?

everything else works awesome running Build #2815

@Maroseliss

I tried those before I asked and they didn't appear to work. I ended up just adding all the different combinations. Should it matter what group manager I am using? I am using Essentials plug-in Group manager.