Role ping autocomplete

IceNine99
  • Edited

This seems to be consistent across all servers on which I am, including one where I have admin rights. And I think it started with one of the recent updates.

Let's keep it simple by giving you an example. I'm on a server with a role called @Richard. The one user with the role also has a nickname of "Richard". If I start typing "@Rich", the nickname ping shows up in the suggestions list, but the role doesn't. "@ich" makes both the possible pings show up.

My experiments suggest that, when Discord  searches through role names to see which ones it can suggest, it seems to ignore the first character of each role name.

And yet there seem to be no posts about it on the interwebs. Anyone know what's going on?

Edit: OS info

I'm on Windows, using the native app. The web version (tested on Firefox and Chrome) both have the issue for me as well.

A Mac-using friend of mine (macOS Catalina) reported experiencing the same issue (on PTB).

My own Android device doesn't experience this, and neither does the Linux app used by a friend. Said Linux-using friend also reports that the web app works fine for them, using Firefox.

Bigger edit: Actually it just hates caps

I accidentally typed "@rich" with a lowercase r, and noticed that the match list displays the role name correctly. Apparently, the matching algorithm just lowercase-ifies the role names before looking for matches, and is case-sensitive.

I think it's still worth calling it a bug; you'd probably want the matching to be case-insensitive, as is the case on Android.

Even bigger edit: Thanks for fixing this

You da best, Discord. Though I'm fairly certain none of you saw this. :)

0

Comments

2 comments

Date Votes
  • ThreeHappiness

    I am experiencing exactly the same issue. Works fine on mobile, but exhibits behavior above on desktop client. (Windows 10)

    For now I can at least use the workaround of typing the role name starting with the second character, so thanks for that tip!

     
    0
  • IceNine99

    Hey, ThreeHappiness, I edited the post again. The TL;DR is "Alternative workaround: type the role name entirely in lowercase".

    1

Please sign in to leave a comment.