Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

. #8721

Closed
ghost opened this issue Dec 25, 2022 · 2 comments
Closed

. #8721

ghost opened this issue Dec 25, 2022 · 2 comments
Labels
type: feature Request for a new Feature.

Comments

@ghost
Copy link

ghost commented Dec 25, 2022 •
edited by ghost
Loading

No description provided.

@ghost ghost added status: needs triage type: feature Request for a new Feature. labels Dec 25, 2022
@Machine-Maker
Copy link
Member

I believe the upcoming brigadier API will resolve this issue. We probably won't backport Component support to legacy commands when that happens.

#8235

@Owen1212055
Copy link
Member

That is correct.

Legacy Commands will still have to manually define usage. (using legacy text, as there's no reason to use colors here anyways?)
However, the modern brig commands will use the autogenerated usage that brig provides

@ghost ghost closed this as completed Dec 26, 2022
@ghost ghost changed the title Allow components in getCommand()#setUsage() . Oct 21, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: feature Request for a new Feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kashike @Machine-Maker @Owen1212055