search message shows `%s` when no chest is near

[taupemoi]

When no chest is near, the search error message is incorrect, for example:

search bone
returns
Could not find any chests containing %s

If a chest (without bone) is nearby, it correctly returns:
Could not find any chests containing BONE.

Relatedly, if it's not too complicated, adding a separate error message when there are no chests at all (There are no chests within radius ...) could be more informative for the user.

Finally, since search uses the same default radius as all other commands, the documentation should maybe add that one can override that radius by specifying it as a 3rd argument, e.g. search bone [RADIUS]. Maybe having a user command to change the default radius on a per-user base could be useful as well?

[mfnalex]

Thanks, will be fixed

[hippotastic]

I just encountered the same issue (the search command literally outputs "Could not find any chests containing %s." without %s being replaced), so carefully nagging @mfnalex to fix this. 😄

[mfnalex]

oh wut? Did I not fix that? It's been quite a time since your issue lol

[mfnalex]

Fixed in 4.10.3 :)

[mfnalex]

Sorry for the delay, I totally forgot this issue!

[mfnalex]

Reopening this issue for the other suggestions mentioned in the first post

[hippotastic]

You could maybe update the issue title to reflect what's still left to do. Maybe something like this:

/search: new message if no chests are within radius, add optional radius argument