No kit permission required option for /kit view

[Blve151]

I'm trying to be able to have people use "/kit view (kit)" without owning the kit so they can know what's inside of it. It's useful as a utility and in my case I'm trying to make a GUI for most of my plugins where appropriate.

I prefer not to hardcode the items inside the kit and make my own GUI as they can change and it's better overall if my GUI (with three options such, opens another menu with the respective kit names and runs "/kit view (name)" on the player when clicked without needing to also be changed when the kits do. https://files.blu3.dev/TOWnYdW.mp4 (an example of what I mean).

If this isn't added, it should be easy enough to use the API and make a plugin to view a kit without checking but I think it would be a good addition to have in the main plugin.

A simple solution could be a config option such as "kit-view-permission-required", and depending on true or false checks if the user has access to the kit before opening the view menu.

[dualspiral]

I've got things to say about this but I haven't got time to get my thoughts down at the moment, except to say the following.

Please use the template provided when creating any issue. I want to bring in some automation soon and doing what you've just done, that is, delete the template it presents you with because you think you don't need it will close the issue automatically.

The API allows you to get the kit stacks. I have been thinking about how to do this for 2.1. It won't happen for v1.14.x

[Blve151]

Oh my bad sorry, haven''t used GitHub much. Thanks for the reply.