mirror of
https://github.com/PluralKit/PluralKit.git
synced 2026-02-04 04:56:49 +00:00
feat(bot): add new guild settings command
This commit is contained in:
parent
f0436332c0
commit
0473bd8f01
15 changed files with 179 additions and 15 deletions
|
|
@ -159,9 +159,11 @@ You can have a space after `pk;`, e.g. `pk;system` and `pk; system` will do the
|
|||
- `pk;log disable <#channel> [#channel...]` - Disables logging messages posted in the given channel(s) (useful for staff channels and such).
|
||||
- `pk;log enable <#channel> [#channel...]` - Re-enables logging messages posted in the given channel(s).
|
||||
- `pk;log show` - Displays the current list of channels where logging is disabled.
|
||||
- `pk;logclean <on|off>` - Enables or disables [log cleanup](/staff/compatibility/#log-cleanup).
|
||||
- `pk;blacklist add <#channel> [#channel...]` - Adds the given channel(s) to the proxy blacklist (proxying will be disabled here)
|
||||
- `pk;blacklist remove <#channel> [#channel...]` - Removes the given channel(s) from the proxy blacklist.
|
||||
- `pk;serverconfig logclean [on|off]` - Enables or disables [log cleanup](/staff/compatibility/#log-cleanup).
|
||||
- `pk;serverconfig invalidcommanderror [on|off]` - Sets whether to show an error message when an unknown command is sent
|
||||
- `pk;serverconfig requiretag [on|off]` - Sets whether server users are required to have a system tag on proxied messages
|
||||
|
||||
## Utility
|
||||
- `pk;message <message id|message link|reply>` - Looks up information about a proxied message by its message ID or link.
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ If your server uses an in-house bot for logging, you can use [the API](/api) to
|
|||
Another solution is for PluralKit to automatically delete log messages from other bots when they get posted.
|
||||
PluralKit supports this through the **log cleanup** feature. To enable it, use the following command:
|
||||
|
||||
pk;logclean on
|
||||
pk;serverconfig logclean on
|
||||
|
||||
This requires you to have the *Manage Server* permission on the server.
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,11 @@ You can also do the reverse operation by passing a Discord account ID (or a @men
|
|||
Both commands output a system card, which includes a linked account list. These commands also work in PluralKit's DMs.
|
||||
|
||||
### System tags
|
||||
A common rule on servers with PluralKit is to enforce system tags. System tags are a little snippet of text, a symbol, an emoji, etc, that's added to the webhook name of every message proxied by a system. A system tag will allow you to identify members that share a system at a glance. Note that this isn't enforced by the bot; this is simply a suggestion for a helpful server policy :slightly_smiling_face:
|
||||
A common rule on servers with PluralKit is to enforce system tags. System tags are a little snippet of text, a symbol, an emoji, etc, that's added to the webhook name of every message proxied by a system. A system tag will allow you to identify members that share a system at a glance.
|
||||
|
||||
You can enforce system tags for all PluralKit users in your server with the following command:
|
||||
|
||||
pk;serverconfig requiretag on
|
||||
|
||||
## Blocking users
|
||||
It's not possible to block specific PluralKit users. Discord webhooks don't count as 'real accounts', so there's no way to block them. PluralKit also can't control who gets to see a message, so there's also no way to implement user blocking on the bot's end. Sorry. :slightly_frowning_face:
|
||||
Loading…
Add table
Add a link
Reference in a new issue