mirror of
https://github.com/PluralKit/PluralKit.git
synced 2026-02-04 04:56:49 +00:00
fix: get rid of top-level guild_id key in dispatch payloads
This commit is contained in:
parent
a4a5f5c17a
commit
d28e99ba43
7 changed files with 11 additions and 12 deletions
|
|
@ -29,11 +29,8 @@ PluralKit will send invalid requests to your endpoint, with `PING` event type, o
|
|||
|signing_token|string|the [signing token](#security) for your webhook URL|
|
||||
|system_id|string|the system ID associated with this event|
|
||||
|id|string?|the ID of the entity referenced by the event (can be a system/member/group/switch/Discord user ID)|
|
||||
|guild_id|snowflake?*|the ID of the guild where this event occurred|
|
||||
|data|object?|event data|
|
||||
|
||||
\* only sent for guild settings update events. in message create events, the guild id is sent in the `data` object as `guild` key
|
||||
|
||||
## Dispatch Events
|
||||
|
||||
|name|description|content of `data` object|notes|
|
||||
|
|
|
|||
|
|
@ -104,6 +104,7 @@ Every PluralKit entity has two IDs: a short (5-character) ID and a longer UUID.
|
|||
|
||||
|key|type|notes|
|
||||
|---|---|---|
|
||||
|guild_id|snowflake|only sent if the guild ID isn't already known (in dispatch payloads)|
|
||||
|proxying_enabled|boolean||
|
||||
|autoproxy_mode|autoproxy mode enum||
|
||||
|autoproxy_member|?string|must be set if autoproxy_mode is `member`|
|
||||
|
|
@ -123,5 +124,6 @@ Every PluralKit entity has two IDs: a short (5-character) ID and a longer UUID.
|
|||
|
||||
|key|type|notes|
|
||||
|---|---|---|
|
||||
|guild_id|snowflake|only sent if the guild ID isn't already known (in dispatch payloads)|
|
||||
|display_name|?string|100-character limit|
|
||||
|avatar_url|?string|256-character limit, must be a publicly-accessible URL|
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue