Revivify commands.yml

Is your feature request related to a problem?

Based on the discussion here and this message.

tl;dr of this. is discussion about the usefulness of the various old configuration files - in this case - commands.yml

Describe the solution you'd like.

If we're going to touch commands.yml, it's a good time to make it even more useful and give it some more abilities that will save time from making or looking for plugins having to do with the simplest things regarding commands.

• ability to create commands with basic functionality, like command that sends minimessage message to the command sender
• ability to set associated permission to the created command or an alias

Describe alternatives you've considered.

Using messy plugins like mycommand or skript to alias or create commands that just send text back, which is not ideal, because the aliases made by those commands are usually just executing multiple commands at once instead of properly registering an alias.

Other

I will update the issue with any good proposals discussed in the discord thread and here

Start by reviewing the existing commands.yml configuration and the linked Discord discussion. Define the supported command message and permission or alias behavior before locating the relevant Paper command-registration entry points. Done means the proposal has an agreed scope and documented behavior for these configuration abilities.