fix(docs): Correctly display bellhop emoji in user guide

This commit is contained in:
Petal Ladenson 2026-01-11 15:56:34 -07:00 committed by GitHub
parent 1776902000
commit 49bc3c0981
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -453,7 +453,7 @@ You can
#### Pinging the user who sent it #### Pinging the user who sent it
If you'd like to "ping" the account behind a proxied message without having to query the message and ping them yourself, If you'd like to "ping" the account behind a proxied message without having to query the message and ping them yourself,
you can react to the message with the `:bell:` :bell: emoji (or `:bellhop:` :bellhop:, `:exclamation:` :exclamation:, or even `:ping_pong:` :ping_pong:), and PluralKit will ping the relevant member and account in the same channel on your behalf with a link to the message you reacted to. you can react to the message with the `:bell:` :bell: emoji (or `:bellhop:` :bellhop_bell:, `:exclamation:` :exclamation:, or even `:ping_pong:` :ping_pong:), and PluralKit will ping the relevant member and account in the same channel on your behalf with a link to the message you reacted to.
## Autoproxy ## Autoproxy
The bot's *autoproxy* feature allows you to have messages be proxied without directly including the proxy tags. Autoproxy can be set up in various ways. There are three autoproxy modes currently implemented: The bot's *autoproxy* feature allows you to have messages be proxied without directly including the proxy tags. Autoproxy can be set up in various ways. There are three autoproxy modes currently implemented: