Description

The idea is that it'll tell you what commands have conflicts and how to fix it

Proposed Behaviour

"/lp conflicts" would pull up a list of all the commands that have conflicts with other things, such as essential's "/vanish" vs super vanish's "/vanish"

"/lp conflicts " would tell you what you'd have to do to fix the confliction, such as adding it to the commands.yml file, it would tell you what you'd need to input exactly, some plugins have it setup so its not the exact same as the plugin name, For example:
sell:

• economyshopgui-premium:sellall $1-
  shop:
• economyshopgui:shop $1-

Extra Details

No response

Side note: im extremely new to this website's functions so if i missed an already created suggestion/request of the same manner Im sorry, wasnt intentional.

While I do like this concept, I don't see why this is something Luckperms should add. Doesn't seem related to permissions at all.

I mean, ig not, but it would be super helpful in the process of setting them up

I think there could also be a /lp conflit command to see what permission nodes are available for a command (used to know when there are multiple permissions for the same command from different plugins) it would be like

/lp conflict command kick
With the result being
essential.kick
UltraPunishments.kick

it is impossible for LuckPerms to accurately determine what permissions a command may check, especially with just the name of the command. if you need to see what permissions a command checks, you can use the verbose command.

This is out of the scope of LuckPerms and would be a much better fit as a separate admin-helper plugin, and there are a few points that make this either simply not fit or just infeasible in LP:

• LuckPerms is a plugin to manage permissions, not commands; while some permissions are "tied to" commands, that does not tie LP to command handling, and plugins can check for permissions outside of commands and this is quite specifically a command resolution issue regardless of permissions

• This is only a "solvable problem" in Bukkit-based servers (Spigot, Paper, ...) because:

  • It is (to my knowledge) the only platform that uses the plugin name for command namespacing, which lets such conflicts be resolved
  • Other platforms (Fabric, BungeeCord, ...) handle commands in different ways, either silently disallowing for such conflicts (meaning a conflict exists, but there is no way to know of its existence) or, hopefully, them somehow resolving it in some harmonious way

  resulting in a disconnect between platforms if this was introduced

• For the second suggestion @LeotomasMC already pointed out why it isn't feasible