Guilds and Members

Fetch one filtered audit page with referenced users and webhook metadata that excludes tokens

Supply cursors and filters in AuditLogQuery. A deletion duration that cannot be represented as safe integer milliseconds fails with reason response, without returning a partial page. The returned page is frozen and remains in memory while the caller retains it

Read filtered audit entries newest first, buffering one page and never prefetching

The maxItems option is required. The pageSize option defaults to 50 and accepts 1–100, maxPages defaults to the pages maxItems needs at pageSize plus 100, and timeoutMs applies to each page. An empty page or maxItems ends the scan, not a short page. Invalid traversal input, a stalled cursor or reaching the page budget fails with PaginationError. Remote failures keep auditLogs.fetchPage's errors. Deletion durations are rounded to whole milliseconds, and one whose milliseconds are not a safe integer fails its page before that page's entries are delivered. Each consumption is independent, and client closure releases the page and fails the next pull. Already delivered entries remain with the caller, and concurrent changes can prevent a complete scan. Use fetchPage instead to also receive referenced users or webhooks

Submit a community's application to the public directory

ManageGuild, enabled discovery and current Fluxer eligibility are required. An existing pending or approved application fails remotely. Eligible verified or partnered communities may be approved immediately. The returned stored application does not guarantee approval or search visibility. An unknown outcome may already have submitted or published the listing. Check fetchStatus before trying again

Change supplied fields of a pending or approved directory application

ManageGuild and enabled discovery are required. At least one field must be supplied, and omitted fields remain unchanged. Tags use the input type's normalization and replacement rules. No old application is fetched or merged automatically. Updates to an approved listing can become public, while search-index updates can lag or partially fail

Fetch directory category IDs and Fluxer's category labels in provider order

This requires an authenticated client, not membership of a particular community or ManageGuild. No category copy is kept

Fetch a community's current directory eligibility and application state

Use a decimal guild ID with ManageGuild permission. A result with eligible false can mean discovery is disabled or the member threshold is unmet, without distinguishing them. The resolved instance's discoveryEnabled value shows whether discovery is switched on. Eligibility can change before application. Reviewed or removed applications include their available reasons

Fetch one page from the current public community directory

The limit option defaults to 24, and offset defaults to 0. Pages can change between reads, so offset-based scans are not a stable snapshot. This neither joins a community nor caches its directory entry, and needs no gateway connection. Eligible read failures are retried as described for this namespace

Withdraw a pending application or remove an approved directory listing

ManageGuild and enabled discovery are required. HTTP 204 succeeds with no value. A missing application is a remote error, not an assumed successful no-op. Fluxer removes the application record and may separately remove its feature or search entry. The community and its members remain, and the prior application is not restored. An unknown or partial outcome needs remote inspection and may require operator recovery, not blind replay

Irreversibly delete this bot's entire authored message history across one community

Use a decimal guild ID. Other authors' messages are preserved, and the bot stays in the community with the same roles

Change only supplied community settings that a bot may edit

Omitted fields remain unchanged, and no old settings are fetched or merged automatically

Set a community's custom invite code, replace it, or pass null to remove it

The code must already be lowercase, 2–32 ASCII letters or digits with single internal hyphens. No automatic normalization is performed

Fetch a community's identity and settings by decimal ID

Fluxer requires membership. The result is a frozen snapshot. This does not fetch or keep nested members, roles or channels, or infer counts or completeness

Request fresh, visibility-filtered counts for 1–100 communities over the connected gateway

Use distinct positive decimal IDs without leading zeros, no greater than "9223372036854775807". The IDs are copied when execution starts. Every community must belong to a ready shard assigned to this client. An unassigned or unready shard fails with notConnected, not an omitted result. The result contains frozen counts and omittedGuildIds in requested order. An omitted entry is unavailable, not zero, and does not explain why it is missing. Community counts are separate observations, not one consistent snapshot. A missing whole reply fails with timeout

Fetch one page of communities this bot belongs to, ordered by ascending guild ID

The limit option defaults to 200 and accepts 1–200. Choose either before or after, not both. Those cursors refer to existing memberships, and if a cursor community was removed, Fluxer may restart the page. The withCounts option defaults to false. Permission bits or requested approximate counts may be omitted, and an omitted value means unavailable, not zero. The frozen summaries do not read or populate the guild cache. No gateway connection or further page traversal is performed. Shared guild deadlines, retries and failures apply. This page is not a complete membership inventory or proof of matching gateway state

Fetch a community's custom invite code, URL and use count with ManageGuild permission

A null code and URL means the community has no custom invite. The read is remote, without a vanity cache or gateway connection. Shared guild read retries, deadline, cancellation and failure rules apply

Look up a community in the enabled guild cache, without a request or gateway connection

The result is undefined when caching is disabled or the entry is absent, expired or evicted. Cached data may be stale, so use fetch for a remote read. A hit becomes more recently used without extending expiry. An invalid ID is misuse: The default API throws GuildOperationError with reason input and the native API dies with it. A closing or closed client has no cache, so the result is undefined

Read the bot's community memberships in ascending ID order, retaining one page and never prefetching

The maxItems option is required. The pageSize option defaults to 200, maxPages defaults to the pages maxItems needs at pageSize plus 100, and timeoutMs applies to each page. Iteration ends at maxItems or an empty page, not a short page. A repeated or backward ID after a removed cursor fails with PaginationError cursorStalled before delivering that page. Other traversal failures are input and pageLimit, and remote failures keep fetchPage's error. Each consumption copies inputs independently. Client closure releases the page and fails the next pull. The withCounts option applies to every page, but missing permission bits or counts remain unavailable, not zero. No gateway connection or cache fill is needed. Already delivered communities remain with the caller, and separate pages do not guarantee a consistent inventory

Remove this bot from one community while preserving its authored messages

HTTP 204 completes the removal, without waiting for a gateway event. The client remains usable for other communities

Grant one role to a member without replacing their other roles

Use a decimal role ID, excluding the implicit everyone role. Fluxer requires ManageRoles and checks hierarchy. HTTP 204 succeeds with no value, not an event acknowledgement or proof the role was previously absent. Fluxer currently accepts auditReason on member-role add and remove routes without retaining it in an audit entry. The example collects one future reaction addition before assigning the role. It needs a connected client, an existing message in this community and a role the bot can assign, and a timeout can collect nothing. It is not a persistent reaction-role system and does not revoke roles on removal

Ban a user from a community, including a user who is not currently a member

Pass decimal guildId and userId. The default ban is permanent and deletes no messages. Fluxer requires BanMembers and checks role hierarchy. In a community whose mfaLevel is GuildMfaLevels.Elevated, the call fails with reason rejected, HTTP 400 and apiError.code twoFactorRequired, unless the bot owns the community or its application owner has two-factor authentication enabled. HTTP 204 succeeds with no value, without waiting for an event

Clear a member's timeout and return the HTTP member snapshot

This sends null rather than a negative duration. The timeout method's permissions, deadline, execution, cache and failure rules apply. No gateway event is awaited

Disconnect one observed voice connection, or all active connections if target.connectionId is omitted

MoveMembers is required. The returned member follows HTTP, without waiting for voiceStateUpdate. A repeated call can fail because the member is no longer connected. The move method's deadline, audit, permission and cache rules apply. An unknown outcome needs later observations rather than blind replay

Change this bot's community profile, not its global account or another member

Omitted fields stay unchanged, and null clears an override. An empty input or unknown key fails locally. Fluxer checks permissions and field-specific rate limits. Avatar, banner, bio and accentColor can be silently ignored without the community-profile entitlement. The returned member excludes bio and pronouns, so success does not prove those fields were stored. Writes with unknown outcomes or cancellation remove the affected cache entry. A definite rejection preserves the old snapshot

Fetch one community member by decimal guildId and userId

A missing member fails with reason notFound rather than an empty result

Fetch a community's current full ban list with BanMembers permission

Results are frozen. There is no ban cache, pagination or guaranteed order. Separate reads are not one consistent snapshot. Shared guild deadlines and read retries apply. A malformed response fails rather than producing a partial list

Check whether the bot, or the member named by options.actorUserId, is above a target member in the community's role hierarchy

Pass actorUserId to check a moderator who ran a command, such as { actorUserId: message.author.id }. The helper fetches fresh guild, actor member, target member and role data in parallel, then applies hierarchy.canManage. One default deadline, rest.defaultTimeoutMs (30,000 ms unless configured), covers those reads. Failure or cancellation waits for sibling request cleanup. No cache is read first and no helper result is retained, but underlying reads can still populate enabled resource caches. A true result covers only hierarchy using four separate observations that may change before an action. It does not check permission bits or MFA, authorize an action or perform it

Fetch one page of members ordered by ascending user ID

The limit option defaults to 100 and accepts 1–1,000. Use the last returned userId as after for another page. Inputs are copied when execution starts. A malformed page fails as a whole. An empty page ends a scan, but no hasMore guarantee or automatic traversal is provided. Separate pages are not one consistent membership snapshot

Fetch this bot's membership in a community without knowing its user ID

No gateway READY event or connection is required

Look up a community member by decimal guildId and userId in the enabled cache, without a request

Enable cache.members to retain members, and cache.roles for local role-name lookup. Explicit fetches or later gateway events can fill those caches, including the author or actor member that Fluxer attaches to message, reaction and typing events, so a member who just spoke can be present without a request. The cache misses, stale-snapshot warnings, misuse and recency rules of guilds.get apply. The example makes no requests when rendering observed role names. A missing member gives undefined, and missing role names fall back to IDs. Observed names are not effective permissions or proof of a complete role list

Look up this bot's own membership of a community by decimal guildId in the enabled member cache, without a request

The result is undefined while the bot's account ID is unknown, which READY or a successful members.fetchSelf supplies, and when cache.members is off or the member is not cached. Each guildCreate event stores the bot's own member. Those sent while a session starts list it by account ID only, and the SDK completes it from READY's account. Successful members.fetchSelf and members.fetch reads and member events store it too. The cache misses, stale-snapshot warnings and recency rules of guilds.get apply. An invalid ID is misuse: The default API throws GuildOperationError with reason input and the native API dies with it. A closing or closed client has no cache, so the result is undefined

Read community members by ascending user ID, without connecting the gateway or downloading the community eagerly

The maxItems option is required, and pageSize defaults to 100, and maxPages defaults to the pages maxItems needs at pageSize plus 100. Each consumption copies inputs and keeps one page, requested only when needed. An empty page or maxItems ends the scan, not a short page. The timeoutMs option applies to each fetchPage call. Remote failures keep that method's error and read retry policy. PaginationError covers input, cursorStalled and pageLimit. Client closure releases the page and fails the next pull with ClientClosedError. Delivered members remain with the caller, and an enabled cache can receive page members. No roles or permission decisions are fetched. Separate pages are not a consistent membership snapshot

Request one community's members over the gateway and deliver frozen batches without accumulating a roster

Choose explicit userIds, a case-insensitive nickname, global-name or username prefix, or all: true. The community and explicit user IDs must be positive decimal strings without leading zeros, no greater than 9223372036854775807. This gateway prefix query is separate from REST member search. Each consumption copies the input and sends one request. The community must have a ready shard assigned to this client, otherwise the request fails with notConnected. Full-list mode is capped by Fluxer at 100,000 members, and Fluxer's server-enforced 30-second limit per bot and community also applies. Only one member stream runs per client, and it uses one of four client-wide gateway slots shared with counts until consumed or released. A full request-slot budget or internal command queue fails with MemberChunkError reason busy. Only a gap on this community's shard ends the stream, while work on healthy shards continues. No connection, REST fallback, cache fill, presence subscription, raw-event forwarding or retries are added

Read unique indexed member-search hits with a bounded scan

The maxItems option is required. The pageSize option defaults to 100 and accepts 1–100, and maxPages defaults to the pages maxItems needs at pageSize plus 100. Each consumption copies filters and their arrays, including recognized inherited and nonenumerable fields, and keeps independent state. Pages are requested only as needed, without prefetch or full-member fetches

Remove a member from the community, succeeding with no value after HTTP 204

Fluxer requires KickMembers and checks hierarchy. In a community whose mfaLevel is GuildMfaLevels.Elevated, the call fails with reason rejected, HTTP 400 and apiError.code twoFactorRequired, unless the bot owns the community or its application owner has two-factor authentication enabled. This does not ban the user, restore membership automatically or wait for a removal event. Missing membership is an API error. Dispatched actions invalidate the member cache even on rejection. The timeout method's execution, deadline and failure rules apply. Writes with unknown outcomes are not replayed

Move a member who is already in voice to a positive decimal voice-channel ID

The target.connectionId value selects one observed connection. Omit it to move every active connection for that member. Fluxer requires MoveMembers and checks hierarchy, destination visibility and permission to connect. Fluxer refuses a move into an occupied voice channel whose participants all use peer-to-peer voice, and the member stays in its current channel. The call then fails with reason rejected, HTTP 400 and details.providerCode USER_NOT_IN_VOICE even though the member is in voice. A retry fails the same way while the destination stays in peer-to-peer mode. The frozen HTTP member result means Fluxer accepted the move, not that the participant has reconnected. A voiceStateUpdate event can first show channelId null, then a new connection ID in the destination. Shared moderation deadlines, auditReason validation, confirmed HTTP 429 retries and member-cache invalidation apply. A lost response or cancellation can leave the move applied. Inspect later observations rather than retrying blindly

Remove one role from a member while leaving other roles unchanged

The addRole method's permissions and completion rules apply. The SDK sends the request even if a local snapshot lacks the role. Success does not prove the role was previously assigned

Search Fluxer's member index for a community, without using or populating the member cache

Without filters, this reads 25 members from offset 0, ordered by newest join time first. Recognized fields, including inherited and nonenumerable fields, are read and filter arrays copied when execution starts. Results can lag membership changes. A result with indexing true means the index is still being built, not that no members matched. An empty result with indexing false can still mean Fluxer's search service is unavailable. Counts do not guarantee completeness, and hits do not trigger full-member fetches

Set or clear the community deafen flag for a member currently connected to voice

Pass { deafened: true } to deafen or { deafened: false } to undeafen. Fluxer requires DeafenMembers and checks hierarchy. The returned member contains isDeafened, without waiting for a voice event. This does not control self-deafen or connect the bot to voice. The move method's deadline, audit, retry, cancellation and member-cache rules apply

Set or clear the community mute flag for a member currently connected to voice

Pass { muted: true } to mute or { muted: false } to unmute. Fluxer requires MuteMembers and checks hierarchy. The returned member contains isMuted, without waiting for a voice event. This does not control self-mute or connect the bot to voice. The move method's deadline, audit, retry, cancellation and member-cache rules apply

Set one member's nickname, or pass null to clear it

A raw empty string fails, while a nonempty string containing only trim whitespace is accepted as Fluxer's clear value. Otherwise, validation removes U+000C and U+202E, trims surrounding whitespace, and requires 1–32 UTF-16 code units. The original string is sent unchanged. Other profile fields and roles stay unchanged. Fluxer checks ManageNicknames, role hierarchy and self-target rules. The frozen result follows HTTP, not a gateway event. Shared guild write deadlines and retries apply. Cancellation waits for request cleanup but cannot undo a dispatched change. An unknown outcome removes the target's cache entry, while a definite rejection preserves it

Replace one member's entire assigned role list in a single PATCH request

Use 0–250 distinct positive decimal role IDs no greater than 9,223,372,036,854,775,807. An empty array clears assigned roles, and the implicit everyone role is rejected as input. IDs are copied by index when execution starts, without fetching or merging the old roles. Fluxer requires ManageRoles and checks hierarchy. This can overwrite concurrent role changes

Temporarily restrict a community member for durationMs milliseconds

The duration must be an integer from 1 through 31,536,000,000 ms. Expiry is calculated when execution starts, so queue and network time consume part of the duration. If expiry is past when Fluxer processes it, the request can clear the timeout. ModerateMembers and Fluxer's hierarchy rules apply, and self and administrator targets are rejected. In a community whose mfaLevel is GuildMfaLevels.Elevated, the call fails with reason rejected, HTTP 400 and apiError.code twoFactorRequired, unless the bot owns the community or its application owner has two-factor authentication enabled. The returned frozen member contains communicationDisabledUntil after HTTP 200, without waiting for an event

Report whether a member is timed out, from the member's communicationDisabledUntil and a moment in time

Returns "active" when the expiry is later than the moment, "none" when the member has no timeout or the expiry is at or before the moment, and "unknown" when the member omits the field, as a gateway member or cached member can. Use members.fetch, which always includes the field, to settle an unknown state. The moment is options.now, otherwise the wall time of the Clock that the client was created with. No request or cache read is made, and connection state is irrelevant, including after client shutdown. A timed-out member keeps its permission bits, but Fluxer blocks sending messages, editing and publishing the member's own messages, reacting, uploading, typing, changing the member's own nickname, writing in threads and joining voice, so check this beside permissions.calculate. A value that is not an object, an expiry that is neither null nor an ISO 8601 timestamp, or an invalid now is misuse and throws GuildOperationError for members.timeoutState with reason input in both APIs

Remove a user's community ban, succeeding with no value after HTTP 204

BanMembers is required. A user who is not banned is an API error, not a successful no-op. The user is not rejoined and queued message deletion is not cancelled. The ban method's execution, failures, cleanup and cached-member invalidation apply