You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using acf-bungee, on completion it suggests an empty argument when there are nothing but subcommands available; it includes all subcommands (as expected), but drops an empty string at the top.
For commands which are simply the root command and have completions set up with @Default, it works just fine:
The text was updated successfully, but these errors were encountered:
It has to do something with the @empty completion as I've seen weird behaviour of it at bungee.
EDIT: The problem is being this line of code. Unlike Bukkit, BungeeCord doesn't check for empty strings and so adds all completions no matter what they are.
This commit fixesaikar/commands#243 .
Some people will ask why not opening a PR in ACF to fix it there? Because in general, BungeeCord shouldn't be adding empty completions!
When using acf-bungee, on completion it suggests an empty argument when there are nothing but subcommands available; it includes all subcommands (as expected), but drops an empty string at the top.
For commands which are simply the root command and have completions set up with
@Default
, it works just fine:The text was updated successfully, but these errors were encountered: