thanks for taking a year to procrastinate on this issue, instead of making a simple decision and or changing 3 lines of code to tidy up the system

The console also can't use minecraft:op or op if you alias both to nothing either to be fair, since aliases are also applied to commands entered on the console.

Forgive the skepticism, your report didn't include the correct YAML for the bug you where trying to report.

no, this is not an intended feature, i spoke with md 5 on saturday at minecon about this issue

so you're telling me the console cant use /minecraft:op if i change that in a permissions.yml that no one running a spigot server uses
i'm more inclined to believe that the commandyml has a problem with it's functions and needs some code to fix it, so i can disable commands from use on the server, and tab complete feature

It's not a bug, what you put in your commands.yml is not valid YAML, or at least it does not mean what you think it means.

I guess by "removed the speech marks when it loaded the file" you mean this:

[18:06:12 WARN]: Could not register alias minecraft:op because it contains illegal characters

I guess commands.yml currently does not support aliases for fallback commands.

I suspect this is an intended feature, the permission system is designed for denying access to commands not aliases.

i'm not interested in a manual workaround, the command.yml's function is to alias or disconnect commands, i would like it to fulfil this function

tried 'minecraft:op':
and it removed the speech marks when it loaded the file

Try:

'minecraft:op': []

Bukkit's yaml parser only breaks keys if they have a '.' in.

Also if you wish to disable the op command a much better way is to add the following to permissions.yml

minecraft.command.op:
    default: false