Brigadier doesn't support aliases, adding the command for each alias inflates the command tree (that's sent to the player) significantly

This is an intentional decision not to create exponentially massive command trees. Brigadier does not have any way to represent aliases and redirects are broken and inconsistent in many ways. If we were to accept something like this it would need to be a per-command-chain option, not entirely sure of the best way to implement that, however.

If we were to accept something like this it would need to be a per-command-chain option, not entirely sure of the best way to implement that, however.

@jpenilla What about adding something like BrigadierSetting.LITERAL_NODE_ALIASES for this? With a note in the javadoc that it results in a massive command tree

BrigadierSettings is not a per-command-chain configuration.

BrigadierSettings is not a per-command-chain configuration.

Well, either way:

• If a command doesn't have literal nodes with aliases, it doesn't need this configuration
• If a command has literal nodes with aliases, it needs this configuration because literal aliases don't work in suggestions or during execution, otherwise there's no point in adding aliases, they don't work without it anyway

So what's the point of per-command-chain configuration?