Discord Mention Generator

A user mention is `<@USER_ID>`, a role mention is `<@&ROLE_ID>`, a channel link is `<#CHANNEL_ID>` and a custom emoji is `<:name:EMOJI_ID>` or `<a:name:EMOJI_ID>` when animated. The client replaces each with a rendered pill at display time; the underlying text is always the raw form.

The ampersand in the role form is the part people forget. `<@123>` and `<@&123>` are different mentions - the first tries to resolve a user with that ID and renders as a broken `@unknown-user` if none exists.

An older user-mention variant, `<@!ID>`, indicated a nickname. Discord accepts it for compatibility but no longer produces it, and both forms render identically. There is no reason to write it in new content.

A mention in a normal message pings. The same mention inside an embed description renders as a pill but sends no notification at all, because Discord deliberately suppresses embed mentions to stop bots from pinging through rich content.

This surprises people building announcement bots: the embed looks right and the mention is highlighted, yet nobody is notified. The fix is to put the mention in the message content alongside the embed, where it will ping normally.

Bots can also control pinging explicitly with the `allowed_mentions` field, which lets a message contain `@everyone` as visible text while notifying nobody. That is the safe default for any bot that echoes user input.

When a bot or webhook sends a mention, it needs the raw mention code. This tool produces exactly the format Discord's API expects.