Skip to content

StringRange not taken into account when mapping Brigadier suggestions to cloud #528

@Machine-Maker

Description

@Machine-Maker

Just add an argument MultiplePlayerSelectorArgument and observe the suggestions don't work past the initial @e suggestion. The cause is that brigadier suggestions, after typing in @e return [. The default suggestion filter removes suggestions that do not start with the current word, in this case @e. If brig returned @e[, then it would work.

I think the best thing, would be to not filter that by default, instead allowing plugins to add such filtering if they wanted. That would mean that within any custom suggestions in custom arguments, you would have to manually match against the current word to return only matching suggestions. Or maybe it could be defined per argument type.

Initial discussion on discord found here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions