Open ThatGhostgirl opened 5 years ago
Adjusting the ordering would be easy enough. It might be better than adding the ID as a search term, since that would slow searches a bit.
If re-ordering, could they all be dated so we have some reference of timeframe for them? I've been around awhile and have a poor memory, the order I have them in gives me a reference of when I learned things. For some reason (staff shared maybe?) some clues do not seem to have a date. And the website doesn't show dates on them at all.
I would find adjusting clue ordering to make my life more difficult for the exact reasons stated about the order being a good reference for when clues were received. I would strongly prefer not changing that unless it's just as a different command switch.
For the initial issue, though: are we talking about large scenes where a clue is being shared and people are trying to see if they have it? Does just doing @clue <clue #>
or @clue/search <clue name>
fulfill this need?
Oh, I see that doing @clue <clue #>
when you don't have that clue just brings up your whole clue list. Maybe if that instead returned something like You don't have clue #<clue number>!
instead that would be more helpful?
Well, that, and, if I do have the clue, some of them are super long, so if I check @clue ### and have it, my screen fills with clue. If it is something difficult, I can live. It's just an inconvenience, nothing major. Might even just be me!
Is your feature request related to a problem? Please describe. With the new numbering system it is difficult to search for a clue by number. @clue/search only works for keywords and the numbering is not in numerical order.
Describe the solution you'd like It would help in large scenes to cut down chatter if we could @clue/search ###