Channels

Create a supported community channel and return its frozen server snapshot

Fluxer chooses the initial position. Omitting permissionOverwrites inherits the selected parent category's overwrites. An empty [] creates no explicit overwrites, which does not make a channel private. Explicit overwrites use Fluxer's required feature opt-in for ViewChannelMembers. Unless the bot has Administrator, each overwrite can allow only permissions the bot has in the parent category, or in the community when there is no parent, and Fluxer answers missingPermissions otherwise. Denies are not checked. Use permissionBits.refusedGrants to see beforehand which bits Fluxer would refuse. Each allow and deny mask must be from 0n through 9_223_372_036_854_775_807n, and invalid masks fail before dispatch. The example denies ViewChannel to everyone and grants access to the named bot. The application manages the created channel afterward. After an unknown outcome, use fetchAll before deciding whether to create again. The result does not confirm gateway delivery

Add one tag to a forum or media channel and return the frozen updated channel

Fluxer requires ManageChannels, assigns the tag's ID, and rejects a tag whose name another tag of the channel already uses, a custom emoji that the community does not have, and a channel that already has 20 tags. Find the new tag by name in the result's availableTags. Fluxer applies the tag like a channel edit, so it emits a Channel Update and an audit-log entry. The SDK reads nothing first, so a channel that is not a forum or media channel fails with Fluxer's rejection. After an unknown outcome, fetch the channel before adding the tag again, because the name is already taken when the first attempt applied

Delete a community channel, succeeding with no value after HTTP 204

No gateway event is awaited and no prior channel existence is proven. The SDK does not fetch the ID first. Fluxer deletes the channel's invites, webhooks, attachments and messages, and detaches a category's children, before it deletes the channel itself. A channel that still exists after a failure may already have lost any of these. A lost response or timeout after dispatch can leave it deleted

Delete one tag from a forum or media channel and return the frozen updated channel

Posts that carried the tag stop showing it. Fluxer requires ManageChannels and rejects a tag ID that the channel does not have, which includes a tag that an earlier call already deleted, and the deletion of the last tag that is not moderated while the channel has ChannelFlags.RequireTag. The call is otherwise an availableTags edit, as createForumTag describes

Change only the supplied channel settings and return the frozen server snapshot

An empty input or unknown field fails locally. Use reorder to change a parent or position. Supply type to convert between Text and Announcement, alone or with other settings. Fluxer requires ManageChannels and rejects converting a text channel that receives follows with CHANNEL_HAS_FOLLOWED_CHANNELS. Converting Announcement to Text queues asynchronous follower removal. Fluxer emits a complete Channel Update with the new type, which replaces the cached observation before handlers run. This call does not await gateway delivery or follower removal. Omitted permissionOverwrites keeps the old list, and [] clears it. Each replacement allow and deny mask must be from 0n through 9_223_372_036_854_775_807n. Explicit replacement handles setting and clearing ViewChannelMembers through Fluxer's required feature opt-in. Unless the bot has Administrator, each changed overwrite can allow, or stop denying, only permissions the bot has in this channel, and Fluxer answers missingPermissions otherwise. Use permissionBits.refusedGrants to see beforehand which bits Fluxer would refuse. On a category, a permissionOverwrites change also writes each child whose overwrites matched the category's old ones, in separate writes. Fluxer offers no way to leave a child out, and permissionBits.sameOverwrites shows which children match. A failure can leave some children with the old overwrites. A retry may skip them, because Fluxer selects children by comparing with the category's overwrites at the time of that call, so fetch the children again to check. The thread defaults and the forum settings apply to the channel types named on each field. The SDK cannot see the channel's type, so Fluxer ignores a setting that does not belong to it. The availableTags list replaces every tag of a forum or media channel, so channels.createForumTag, editForumTag and deleteForumTag are the safer way to change one tag. Pass a received channel's availableTags back to keep all its tags

Replace one tag of a forum or media channel and return the frozen updated channel

This is a full replacement: A moderated value or emoji that the input leaves out becomes false or none instead of keeping its old value, so read the tag first to change only one of its settings. The tag keeps its ID and the posts that carry it. Fluxer requires ManageChannels and rejects a tag ID that the channel does not have, a name that another tag already uses, and a change that would leave a channel with ChannelFlags.RequireTag without a tag that is not moderated. The call is otherwise an availableTags edit, as createForumTag describes

Fetch a community channel by decimal ID and return a frozen snapshot

The ID can name a thread or a forum post, which returns a thread shape, so compare type or use isThreadChannel before reading fields that only some shapes have. A thread has no permission overwrites of its own. A private-channel response fails with a typed response error. Permission overwrites describe explicit settings, not inherited or effective permissions. This neither connects the gateway nor populates a complete community-channel list

Fetch the community channels currently visible to the bot, without pagination

The returned list is a point-in-time snapshot, not a subscription or completeness guarantee. It never includes threads, which Fluxer lists separately: Use threads.fetchActive for the active ones. No members, roles, private channels or missing overwrite targets are fetched

Fetch frozen channel and distinct community follower counts for a viewable announcement channel

Fluxer can cache these counts for up to 60 seconds, so they need not include the latest follow changes. This does not populate channel caches or subscribe to changes. The auditReason option is not supported

Request fresh member counts for 1–25 channels in one community over the connected gateway

Use distinct positive decimal channel IDs without leading zeros, no greater than "9223372036854775807". The community ID must satisfy the same bound. The IDs are copied when execution starts

Follow an announcement channel into the supplied community text channel and return frozen source and webhook IDs

The source must be viewable, have type Announcement and belong to a community with announcements enabled. The target must have type Text, with ViewChannel and ManageWebhooks on that channel plus community-level ManageWebhooks. Fluxer enforces webhook capacity and rejects duplicate source-to-target follows

Look up a community channel in the enabled cache, without an HTTP request or a connection

The result is undefined when caching is disabled or the entry is absent, expired or evicted. The result can be a thread, forum channel or media channel, so compare type or use isThreadChannel before reading fields that only some shapes have. A hit may be stale and becomes more recently used without extending expiry. Use fetch for a remote read. An invalid ID is misuse: The default API throws ChannelOperationError with reason input and the native API dies with it. A closing or closed client has no cache, so the result is undefined

Remove one explicit permission overwrite by decimal role or member target ID

Other overwrites remain unchanged. HTTP 204 succeeds with no value. Fluxer requires ManageRoles. Unless the bot has Administrator, it can remove an overwrite only when it has every permission that the overwrite denies in this channel, and Fluxer answers missingPermissions otherwise. To check beforehand, call permissionBits.refusedGrants with the overwrite as current and undefined as next. On a category, Fluxer writes the category first and then each child whose overwrites matched the category's old ones, in separate writes. Fluxer offers no way to leave a child out, and permissionBits.sameOverwrites shows which children match. A failure can leave some children with the old overwrites. A retry may skip them, because Fluxer selects children by comparing with the category's overwrites at the time of that call, so fetch the children again to check. An unknown outcome needs an explicit follow-up read

Submit community-channel moves, succeeding with no value after HTTP 204

Fluxer applies moves sequentially and may normalize positions. The syncPermissionsOnMove option copies the destination category's overwrites, and applies only to a move into another category. Fluxer copies them after each move, so a failed copy leaves that channel moved without them. Unless the bot has Administrator, the copied overwrites can allow, or stop denying, only permissions the bot has in the moved channel, and the copy fails with missingPermissions otherwise. Use permissionBits.refusedGrants to see beforehand which bits Fluxer would refuse. A bulk channel event can arrive before that copy finishes. Failures can leave partial movement because this is not a transaction, and the error does not list the moves that finished. Use fetchAll afterward when final order matters, and after a failure to read the actual order and parents before sending moves again. The Communities & permissions guide shows how to keep the failure while reading them. Fluxer currently accepts auditReason on this route without retaining it in an audit entry. No reordered list is invented locally

Replace one explicit role or member permission overwrite

Supply the target ID and raw bigint allow and deny flags. Each mask must be from 0n through 9_223_372_036_854_775_807n, and larger received masks cannot be written unchanged. HTTP 204 succeeds with no value. Fluxer requires ManageRoles and uses a feature opt-in to set or clear ViewChannelMembers. Unless the bot has Administrator, the overwrite can allow, or stop denying, only permissions the bot has in this channel, and Fluxer answers missingPermissions otherwise. To see beforehand which bits Fluxer would refuse, pass permissionBits.refusedGrants the current overwrite, the new one and the bot's bits in this channel, from permissions.fetch with a channelId or from permissions.fetchChannels. On a category, Fluxer writes the category first and then each child whose overwrites matched the category's old ones, in separate writes. Fluxer offers no way to leave a child out, and permissionBits.sameOverwrites shows which children match. A failure can leave some children with the old overwrites. A retry may skip them, because Fluxer selects children by comparing with the category's overwrites at the time of that call, so fetch the children again to check. No target fetch or inherited-permission calculation is performed

Add a community member who can view the parent channel to a thread, succeeding with no value after HTTP 204

Adding a current member also succeeds, and otherwise Fluxer posts a RecipientAdd notice in the thread. Fluxer requires Send Messages In Threads, plus Manage Threads in a locked thread and in a private thread that is not invitable, unless the added member can manage threads. An archived thread accepts no new members

Create a thread that is not attached to a message in a text or announcement channel, and return its frozen snapshot

The bot becomes the thread's first member, and Fluxer posts a ThreadCreated notice in the parent channel for a public or announcement thread. Fluxer requires Create Public Threads, or Create Private Threads for a private thread. Use createPost in a forum or media channel. A lost response can leave the thread created, and the SDK never resends it

Start a public thread on an existing message and return its frozen snapshot

The thread takes the message's ID, and the message gains MessageFlags.HasThread. Only a default message or a reply in a text or announcement channel can start a thread, and only one. In an announcement channel the thread is an announcement thread. Fluxer posts a ThreadCreated notice in the parent channel unless the message is among its five newest messages. Fluxer requires Create Public Threads and Read Message History. A lost response can leave the thread created, and the SDK never resends it. After an unknown outcome, channels.fetch(message.id) shows whether the thread exists

Create a post in a forum or media channel, a public thread with its first message, and return both frozen

Files in the message are sent inline as multipart form data in the same request, never through presigned uploads, under messages.send's attachment rules and the client's upload budget. Fluxer requires Send Messages in the channel plus the permissions the message content needs, and applies the channel's tag rules. When the first message fails, Fluxer removes the new post again. A lost response can leave the post created, and the SDK never resends it

Change only the supplied thread settings and return the frozen thread

It uses the route and rate limit of channels.edit. ThreadEdit describes which changes the thread's creator may make and which need Manage Threads

Fetch every active thread the bot can view in a community, newest first, as one frozen list

A private thread appears when the bot joined it or can manage threads in its parent channel. Each thread the bot joined has membership set

Fetch one frozen page of archived threads of a text, announcement, forum or media channel, as ArchivedThreadQuery selects

Scopes "public" and "private" list the most recently archived first, and "joinedPrivate" lists the newest threads first. Each thread the bot joined has membership set. Fluxer requires Read Message History, plus Manage Threads for scope "private"

Fetch one thread member as a frozen ThreadMember

A user who is not a member fails with UNKNOWN_THREAD_MEMBER. With withMember, member holds the user's community membership while the user has one. Its community comes from the channel cache when the thread is cached there, otherwise from one extra channel read that shares the deadline and whose failure fails this call

Fetch one page of thread members in ascending user ID order, as frozen ThreadMember values

With withMember, each member holds the user's community membership while the user has one, with the community resolved as fetchMember describes

Read thread members in ascending user ID order, buffering one page and never prefetching

The maxItems option is required. The pageSize option defaults to 100 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. Invalid traversal input, a stalled cursor or reaching the page budget fails with PaginationError, and remote failures keep threads.fetchMembers's errors. With withMember, one consumption resolves the thread's community once, as fetchMember describes. Each consumption is independent, and client closure releases the page and fails the next pull

Add the bot to a thread, succeeding with no value after HTTP 204

Joining a thread the bot already belongs to also succeeds. An archived thread cannot be joined, and a locked one needs Manage Threads

Remove the bot from a thread, succeeding with no value after HTTP 204

An archived thread cannot be left, and Fluxer rejects a bot that is not a member with UNKNOWN_THREAD_MEMBER

Remove a member from a thread, succeeding with no value after HTTP 204, and Fluxer posts a RecipientRemove notice in the thread

Removing the bot's own ID works like leave. Fluxer requires Manage Threads unless the bot created the private thread. A user who is not a member fails with UNKNOWN_THREAD_MEMBER, and an archived thread cannot change

Search the threads of a text, announcement, forum or media channel by name, tags and state, and return one frozen page

Fluxer requires Read Message History. While Fluxer builds the community's search index it answers HTTP 202 with code SEARCH_INDEX_NOT_READY, which this method returns as an indexing page without retrying. Any other HTTP 202 answer fails with reason response. While Fluxer's search service is turned off, the call fails with reason rejected and apiError.providerCode FEATURE_TEMPORARILY_DISABLED