Members

The members builder allows you to configure a few settings related to guild members.

ExtensibleBot(TOKEN) { // ... members { fillPresences = false fill(TEST_GUILD) } }

Functions

Name	Parameters	Description
`all`		Specify that you want to receive all member entities from all guilds.
`fill`	Collection: `Snowflake`, `String` or `ULong`	Specify multiple guild IDs to request all member entities from. May be called multiple times.
`fill`	`Snowflake`, `String` or `ULong`	Specify a guild ID to request all member entities from. May be called multiple times.
`none`		Specify that you do not want to receive any member entities from all guilds. This is the default behavior.

Properties

Name	Type	Default	Description
`fillPresences`	`Boolean?`	`null`	Whether to request presence information from member entities requested from the gateway. Supply `null` to defer to Kord's recommended default behavior, which is currently equivalent to `false`.
`lockMemberRequests`	`Boolean`	`false`	Whether to force guild member requests to be sequential via a `Mutex`, preventing concurrent requests for guild members. This will significantly slow down requests for guild members, but may help larger bots to avoid hitting a rate limit. We believe there are probably better ways to do this, but we lack the experience with large bots to come up with another solution. If you have any ideas, we'd appreciate it if you'd open an issue or submit a pull request!

Last modified: 03 September 2024