Skip to content

Conversation

ShadowArcanist
Copy link
Member

New

Users can set custom pings/mentions instead of receiving discord notifications with hardcoded @here ping.
image

Why this change?

The main reason for this change is that @here only notifies users who have the Discord app open or running in the background. Even if users open Discord later (in case they didn't had discord running on background), they won’t see a ping for the message where @here was used, increasing the risk of missing critical notifications. Additionally, if many people are online, it will notify all of them, which can become annoying.

Usage

Users have to format the role or user ID using Discord's mention syntax and enter it in the Ping Text field. If this field is left empty, no pings will be sent. The helper text has been updated to guide users on the correct syntax to use
image

Notes:

  • Our current documentation needs a complete rewrite for the notifications section, so this change will be included in the upcoming PR as part of that rewrite.
  • All the changes are done by AI, but tested the changes locally and it's working without any issue, since this affects the database, please double-check this PR!!.

@Cinzya
Copy link
Member

Cinzya commented Sep 30, 2025

So what if people want to keep the @here? Does typing @here work?

Also every user that will run the migration will essentially have their discord pings disabled as it replaces the enabled checkbox with an empty ping text field.

Instead of replacing it completely, I believe it would be better for the users if you add it as an additional field.
So they can choose to keep the default ping behaviour or write a custom one if you get what I mean.

@ShadowArcanist
Copy link
Member Author

So what if people want to keep the @here? Does typing @here work?

Yeah it works if you type @here or @everyone

For the other parts, let me think about it (will have to come with a different approach)

@ShadowArcanist ShadowArcanist marked this pull request as draft September 30, 2025 06:43
@Cinzya
Copy link
Member

Cinzya commented Sep 30, 2025

You can probably adjust the migration to auto fill the new column depending on whether or not the checkbox was enabled.

I'm more wondering if it being just a text field isn't too confusing for people that just want a simple @here or @everyone. Maybe a dropdown could be nice, where you can select between @here, @everyone and Custom where the user can then insert the role id.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants