Add commands for managing operators

[Mickey42302]

Hello,

I would like to suggest implementing commands for managing operators.

Currently, there is no way to change a player's operator level without editing the "ops.json" file. Similarly, you cannot change the value of "bypassesPlayerLimit" without editing the file.

This addition would allow server owners to have more control over players they grant operator privileges to. The "/oplevel" command can be used to change the permission level, while "/bypassplayerlimit" changes the value of the "bypassesPlayerLimit" entry.

There is also an "/opinfo" command, which shows a list of operators and allows you to see information for a specific player.

[davidmayr]

Couldn't this be a plugin instead? If the respective API is missing, it should be added instead imo

[Mickey42302]

I looked into making a plugin. Unfortunately, I could not find a way to change operator levels or the bypassesPlayerLimit flag via the API.

It would also be more helpful to have this built in. Minecraft already has the "/deop" and "/op" commands built into the server.

[electronicboy]

We're not bukkit, and so permissions should not be added to its namespace. Outside of that, generally not fond of adding non-util commands, the ones we do add are generally

1. under the paper command
2. Provided for the sake of debugging stuff which plugins can't cleanly access and are highly useful for debugging specific issues, i.e mob spawning, item data, etc
3. not under the expectation that they'll be used by people outside of these cases and so we don't have things like localisation that would really be needed if we wanted to actually deal with adding extra commands.

I would much rather support expanding the API here and let plugins deal with the utility/command design issues

[Mickey42302]

I made the permissions start with "bukkit" since I was following what I saw in the code for the other commands (such as "bukkit.command.mspt" for "/mspt").

If the API were to be expanded, I'd be willing to create a plugin that utilises it.

[lynxplay]

I 100% agree with cat here, I dont think administrative commands like this are generally something we should keep adding. Not that operator level is even something I'd consider worth using. Operator permissions are pretty broad.

There is a reason the community generally has focused around fine grained permissions for individual commands and features. I don't think it is in our best interest to expand the (imo flawed) operator permission system.

Thank you for the PR anyway!