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
Feature Request: Have the selection embed show what part of input triggered it.
Who would use it? Anyone using commands like !action, or !cast which could have multiple parts to which search and select may apply, wanting to make sure they are replacing the correct input. What part of the bot? general functionality How would it work? Allow get_selection() to be passed a query argument, then display a line of text somewhere indicating what input prompted it. Why should this be added? From time to time I see others as well as myself get confused as to what input there was actually multiple matches for when targeting multiple creatures for example, and being shown exactly what part of your message it was that prompted the multiple matches right there, it would be a lot easier than trying to parse what part of your command set it off.
Byronius#0001
Upvote - steffleupagus#8008
Upvote - purplecharmanderz#6693
Upvote - Stellatrix13#6887
Upvote - Boop#3128
Upvote - justadool#8507
Upvote - merien#7290
The text was updated successfully, but these errors were encountered:
Feature Request: Have the selection embed show what part of input triggered it.
Who would use it? Anyone using commands like
!action
, or!cast
which could have multiple parts to which search and select may apply, wanting to make sure they are replacing the correct input.What part of the bot? general functionality
How would it work? Allow
get_selection()
to be passed aquery
argument, then display a line of text somewhere indicating what input prompted it.Why should this be added? From time to time I see others as well as myself get confused as to what input there was actually multiple matches for when targeting multiple creatures for example, and being shown exactly what part of your message it was that prompted the multiple matches right there, it would be a lot easier than trying to parse what part of your command set it off.
The text was updated successfully, but these errors were encountered: