Orbit 1.12.0: Less Waiting, Clearer Controls, Better Community Tools

The changelog has been quiet for a while. The product has been considerably less quiet, sometimes in ways that were not particularly helpful. This update collects the work since the previous entry: larger improvements to how communities configure and use Orbit, followed by the individual fixes that deserve to be recorded even when they do not deserve a dramatic entrance.

A Dashboard that makes the next action easier to find

The server Dashboard has been refreshed across its core tools, module pages and shared editors. Navigation now includes permission-aware page search, useful breadcrumbs, server switching and section navigation for long settings pages. Search results explain why a page is locked instead of leaving an unavailable destination to explain itself after the click.

The server overview puts identity, connection and setup status, quick actions, enabled features and recent activity in a clearer order. Completed setup checks can fold away, the tool preview expands when needed, and the personal server list supports favourites, persistent grid or list selection, search, sorting and pagination. There is less decorative competition for the same square centimetre.

Fields keep their labels outside the input. Optional guidance can collapse while warnings and restrictions remain visible. Disabled features hide their dependent controls without deleting the saved values. Message authoring uses one meaningful preview per output and preserves repeated spaces, empty paragraphs and trailing line breaks. Mobile navigation has an explicit Close control, and long lists, selected values and action rows wrap more deliberately.

Less waiting between a click and a response

Slash commands now acknowledge before slower permission checks, module preparation and content rendering. Supported module buttons also acknowledge earlier, including Giveaway entry controls. Dashboard module actions reach the Bot without waiting for the old periodic check, and busy work in one server has less opportunity to hold up unrelated actions elsewhere. The first response and the finished result remain separate: accepting an action does not pretend that Discord has already completed it.

Temp Voice now reacts to entering the configured trigger channel using the destination voice state. Muting or deafening in the same channel does not start another creation attempt. Overlapping join events share one creation, and a channel that has genuinely been deleted can be replaced instead of leaving its owner stuck behind an obsolete room record. A temporary Discord lookup failure does not create a duplicate room.

Dashboard sections can appear as their own data becomes available, rather than waiting for the slowest neighbouring panel. Recent content stays visible during refresh, ordinary filter changes avoid unnecessary page-wide loading, and a confirmed save is immediately reflected when a view is reopened. Login, translations and account loading now have clearer retry states; a connection failure no longer invents a generic account or displays translation identifiers as interface text.

Server setup explains the choices before making them

Setup now uses six visible steps with progress, server-profile recommendations, explicit module limits and an editable launch summary. Language and profile choices open without waiting for every Discord resource to load. Directory presentation and the installer welcome have distinct previews, and the welcome channel remains selected when its delivery switch is temporarily turned off.

The invitation flow offers Easy and Advanced permission choices with an explanation of their effect. Permission groups show selection counts and can be filtered to recommended choices. Setup also shows the capabilities available in each channel and category, including sending messages, reading history, attaching files, managing messages and working with voice channels. Search, a last-update indicator and explicit refresh make that information usable.

Four protection levels explain what AutoMod will do, rather than relying on increasingly serious adjectives. Features that need missing Discord permissions are shown as unavailable, and final setup checks the selected language, locked choices and enabled welcome settings again. An attractive preview has finally stopped being accepted as proof that the Bot can perform the action.

Leveling now follows the milestones your community defines

Leveling is now organised around configurable XP milestones. Server managers can define positive, zero and negative thresholds, give them names, add or remove several roles, and describe benefits or restrictions. Positive progress and negative consequences follow their own thresholds. The preview shows which milestone is current and what its role changes would mean at the selected XP value.

Role effects can accumulate across reached milestones or belong only to the current rank. New milestones default to current-rank roles; existing configurations keep their cumulative behaviour. Benefits and restrictions remain cumulative descriptions. When a temporary remove-role consequence stops applying, Orbit restores the member's recorded role baseline rather than treating every absent role as permanently lost.

Member Profiles now present signed XP, the current named milestone, cumulative benefits and restrictions, and the actual role consequences before moderation history. Authorised staff can set an exact XP total or apply a signed adjustment and see the result immediately. Discord role changes follow afterwards; a missing permission or failed assignment is displayed as a real delivery problem, rather than an indefinitely optimistic 'will be added'.

The public member card remains available through /leveling card, with configurable fields, templates and appearance, ranked XP and message statistics, and progress towards the next positive milestone. /leveling leaderboard handles tied scores consistently. /orbit profile provides a short-lived link to the caller's own restricted member profile without requiring Moderation to be enabled. Bonus Challenges still earn normally; their removed standalone command does not remove the challenges themselves.

Forms can ask for corrections without starting over

Needs Changes now creates a proper correction loop. Respondents receive a correction link, reopen their existing answers and retained attachments, and submit another review cycle on the same response. Identified respondents must return with the original Discord identity. Reviewers keep the history, and later changes to a form no longer silently rename the questions shown on an older response.

Review notes can be edited, pinned, unpinned and removed without rewriting the decision history. Approval and rejection have an explicit respondent-notification choice; identified respondents are notified when corrections are requested. A failed Discord notification does not undo the review decision. Responses that lack a trustworthy historical question snapshot remain reviewable, but Orbit does not guess a replacement form for their correction link.

Conditions and scoring now bring answer rules and role automation together. Submission, approval and rejection can each have their own role additions and removals, with matching and fallback effects. Date conditions can compare calendar days, months or years. Existing approval-only rules retain their approval timing; new phase-specific rules run at the phase selected in the editor.

Question types use a searchable picker with descriptions. Text comparisons accept removable values, and choice comparisons can match several options. Disabled Auto Review hides its scores and conditions while keeping the configuration. Date answers accept a broader range of human formats, including written month names; ambiguous numeric dates follow the respondent's locale before being normalised.

Moderation shows the context behind the action

Moderation settings now separate reviews, warnings, member messages and direct links into focused tabs. The case view gives status and actions more room, filters line up properly, and message controls appear only when their delivery is enabled. Kick and ban notices are sent before removing the member, so the explanation is not left trying to catch someone after the door has closed.

Automatic case priority now considers the action, timeout duration, recent successful cases, repeated actions, active warnings, earlier removals and Raid or Scam context. Automatic priority ranges from Low to High; staff can choose Critical explicitly and inspect the original factors. The result is a clearer triage aid, not a claim that a priority label determines guilt.

Current Discord administrators can search and read Member Profiles in ordinary server mode. Manage Server alone does not grant sensitive profile access, and editing notes or correcting XP still has its own permission requirements. Optional live role checks can fail independently while durable profile information stays available and the unverified state is clearly marked.

AutoMod explains what it checks

AutoMod navigation follows the same structure as the sidebar. Editing a preset-managed rule shows a clear warning, Raid settings omit unrelated message controls, and sanction cards explain their requirements. AI settings disappear when no usable model is available. Scam guidance describes checks of message text, supported images and public linked-page text, including the cases that cannot be checked. Image similarity is described as a fingerprint match, not a probability that someone acted maliciously.

Sentinel reports and decisions are easier to understand

Eligible Sentinel reports can now identify the Discord subject directly, with optional detailed receipts and results in the server's selected channel. Participant-facing outcomes can include a clear explanation and additional remarks without publishing confidential review notes. Accepted or declined results state their grounds and consequences without pretending that Orbit is a court.

Public-name-only report attribution now stays limited to that name. It does not expose an account or Discord identifier, avatar, staff position or richer profile to the receiving server. Affected users can reach their own Standing and Sentinel support context through the ordinary Support workspace; unrelated support-intake restrictions do not remove those authorised routes.

Tickets have a clearer life after opening

Ticket settings now define open and closed categories, transcript capture, a transcript-notification channel and whether a summary is posted when a channel is deleted. Closing can move the channel into the chosen closed category. Retained transcript summaries include the opener, deleting actor, message and contributor counts, and an authenticated Dashboard link. Authorised staff can separately delete captured transcript messages while retaining a minimal deletion record.

New Ticket creation returns the usable channel link before secondary welcome and logging work. If the welcome message fails, Orbit explains that the channel already exists instead of inviting another creation attempt. Claim, release and close actions resolve their response labels together, and queued changes refresh the Ticket list, statistics, details and templates.

Managed panel posts remain tied to the panel's saved revision across their selected channels. Deleting a panel message in Discord releases that exact placement, including bulk deletion and later reconciliation of a missed event. Temporary Discord failures preserve the placement rather than incorrectly freeing its slot. Lowering a posting limit does not destroy existing posts, and live refresh no longer overwrites an unsaved Ticket settings draft.

Giveaways and Suggestions keep the participant's state straight

Giveaways

Public Giveaway cards are more compact. Private Details shows the participant's actual entry state, eligibility, bonuses and an understandable explanation of draw verification, with the appropriate Enter or Withdraw action. Entry confirmation is delivered before the public card refresh, and module links open the current workspace rather than retired pages.

The editor retains its draft until the requested action has actually completed. An unresolved result cannot be submitted again as if nothing happened, a completed save is not reported as failed merely because its subsequent refresh failed, and Discard restores the existing Giveaway with its identity intact. An uncertain Discord edit no longer triggers an automatic duplicate publication. Rerolls still require a fairness justification, and manual prize completion still requires delivery confirmation.

Suggestions and Roadmap

Members can use /suggest comment when public comments are enabled. Cards, workflow labels, Roadmap summaries and confirmations follow the server's language. Private staff notes no longer inflate the public comment count, and disabled downvote or vote-removal actions are not offered as working controls.

Duplicate merges now move votes in resumable batches, preserving existing votes at the destination and keeping counts consistent. A larger board no longer has to finish the entire merge in one interaction. Pending transfers stay visible, and a closed destination pauses the merge until it is reopened instead of silently losing the remaining work.

Game nights with fewer disagreements about what just happened

Party Hub

Party games reject answers after the server's deadline and calculate speed from when the answer actually arrives. Submitted votes, slogans and drawing ratings stay locked. Slogan Swindle keeps its real answer private until the reveal, and Cooperative Song Line continues beyond the first correct word while rotating the appropriate team writer. Joining a room no longer includes an artificial multi-second wait.

Detailed drawings fit the supported live-message size, private image-position previews no longer flood the connection, and ratings require an explicit choice. Song Line now uses six sourced historical song texts with visible attribution instead of fabricated lyrics. This is a small historical collection, not a modern music catalogue; very detailed drawings can still lose fine detail when simplified for delivery.

Casino

Blackjack now handles player and dealer naturals correctly: matching naturals push, a drawn 21 does not beat a dealer natural, and insurance depends on an actual dealer blackjack. Double-down is limited to the opening two cards. Hold'em keeps unrevealed turn and river cards hidden, including private-hand inspection, and overdue interactive sessions retain the information needed to recover reserved stakes.

Casino management separates balance adjustments from account locks and shows the fields for the selected operation. Expired exclusions are no longer presented as active locks. Unavailable actions respect the module's state, number formatting follows the current locale, and narrow-screen rows keep their balance and status information readable.

Creator Notifications now handles pauses, archives and uncertainty

Creator groups and sources have explicit archive, restore and eligible permanent-removal actions. Archived configuration no longer consumes active capacity or appears in notification previews. Restored groups return paused, so restoring a record does not unexpectedly resume delivery. Groups with delivery history remain archived rather than offering a deletion that would erase that history.

Changing a panel, moving a source or archiving a group updates the affected live Discord messages as well as the Dashboard. Live and content monitoring are handled independently: a failed video check cannot masquerade as an offline stream, and an unknown status does not prematurely finish the live notification. Repeated live edits and later recovery are no longer permanently suppressed by an earlier attempt.

Group cards expose the monitoring checks and errors that Twitch, YouTube and TikTok actually support, with collapsible details and delivery history. YouTube handles and channel URLs are normalised correctly. TikTok public-video retrieval has a fallback, but its public endpoints can still change or reject access; a failed check is shown as uncertainty rather than manufactured content or a false status.

Module updates respect what is actually required

Optional integrations no longer install, activate or request consent for an unrelated module. Store dependency links distinguish required dependencies from optional connections. A version-change preview evaluates the proposed version's capabilities rather than rejecting them simply because an older version is currently installed.

Installation and update actions open their concrete impact review directly, with explicit capability acceptance and completion controls. Reset returns to the actual saved update policy. An unavailable module explains its state in Discord instead of leaving a button unanswered, and recovered modules restore their commands. Version-specific fixes apply to the matching module release; an explicitly pinned installation is not silently moved to another version.

Developer Center access now follows current team membership and application status consistently. A suspended account cannot retain access through a team, and transferring a module does not leave the former creator with an unrelated ownership override. Renewed Developer Terms require an explicit acceptance of the displayed version, including for eligible team members; accepting terms does not itself approve an application.

API tokens with a readable scope

Account API tokens support exact endpoint selection, expiry and optional IP or CIDR restrictions, with the secret shown only once. The endpoint catalogue provides descriptions, read, write and live labels, HTTP method information, search, filters and pages. A supplied eligible token can be activated for a scoped Dashboard session, which shows the effective account and provides a return to the personal session. Browser-only security actions remain outside token access.

Your Discord application, with Orbit doing the work

For accounts enabled for Custom Bots, the invitation flow now supports delegating operation of an owned Discord application to Orbit. Setup verifies the application and its required access, records the operating authorisation for the explicitly selected servers, and offers a permission choice for installation. This lets an eligible community use its own Bot identity with Orbit's supported tools.

Owners can manage the application, rotate its credential, stop operation and explicitly release server assignments. A paused or stopped custom assignment does not silently switch to the official Orbit Bot. Stopping removes the stored operating credential; changing back to another Bot identity is a separate, deliberate action. Credentials are excluded from ordinary views, personal-data exports and authorisation documents.

Permissions and change history explain their effect

Roles and Permissions focuses on one selected permission, with separate catalogue and detail panels, collapsible filters, larger role choices and a change summary that appears only when needed. Managers can copy assignments from another permission and add individual allow or deny exceptions. These edits share the existing draft, reset and save flow.

Command access starts with switches for complete command groups. Disabling a group removes it from the server's Discord command registration. Advanced rules, channel restrictions and the access preview remain available when needed. Channel and category allowlists or blocklists are explained together: every matching rule must permit the invocation, so a broader allow does not quietly erase a more specific denial.

Routine changes no longer interrupt the save with a popup for an optional audit message. Successful audited changes offer Add message, and history supports adding, editing or clearing that supplemental text. Required server reasons stay mandatory in the active form; fairness, delivery and safety explanations keep their own requirements. Change History now uses readable action and target names, concise summaries and field-level comparisons, while preserving the facts older records actually contain.

Support starts with the request, not the department chart

Support has a new requester ticket list and conversation workspace. Creating a ticket starts with searchable request types beside a larger message form, related-server selection, field validation and up to five private attachments. Each type explains its eligibility before submission, including any account, server, setup or plan requirement. Existing conversations remain reachable when new-request intake is paused.

The conversation keeps its request type and relevant context, with public reply attribution separated from private staff notes. Ordinary Support and Sentinel inbox access no longer adds a blanket second-factor hurdle. Existing permissions and confirmation requirements for sensitive actions remain. Requests about the affected user's own Standing or Sentinel entry keep their authorised contact path even when ordinary support intake is restricted.

Feedback uses a responsive composer and can include per-operation API timings to help explain a reported wait. Requester updates preserve paragraphs and stay separate from private handling notes. Where a feedback reward is offered, a failed delivery retries the original amount and currency rather than allowing an ambiguous result to become a different reward.

Public pages and privacy information are easier to reach

orbot.cloud is now the primary public Orbit address, with registered legacy domains remaining usable. The homepage, feature hub, individual feature pages and setup guide explain the product more directly. Published blog and changelog entries have complete readable pages, paginated archives and RSS feeds. Returning from a public page to the Dashboard no longer leaves the wrong navigation shell attached to the destination.

Terms and Privacy edition 6.0, effective 28 September 2026, use a shared reading layout with contents navigation, stable section links, clearer typography and a complete body that works without JavaScript. The documents group related services and explain optional functions, protective restrictions, data handling and user rights more directly. Developer Terms have their own updated agreement and versioned acceptance. Links to older legal sections retain their corresponding destinations.

Personal-data exports keep their temporary archive available until it has been handed to private storage. Failed requests do not consume the successful-export cooldown and can be dismissed immediately. Completed export history can be dismissed after one calendar year; that hides the account's history entry rather than pretending to recall a file already downloaded. The export page also puts its storage and retention explanation beside the action in ordinary readable text.

Limits worth knowing

• Discord rate limits, missing permissions and external outages can still delay an action; an early acknowledgement is not its final outcome.
• Live role verification can be unavailable while durable Member Profile data remains readable; current authorisation is still required.
• Forms cannot offer a safe correction flow for an older response whose original question definition is unavailable.
• A Creator group with delivery history remains archivable and restorable, rather than permanently deletable.
• TikTok public endpoints can change or block access independently of Orbit.
• Party Hub bundles six historical song texts; modern songs require an appropriately licensed source.
• Large Party drawings can lose fine detail when simplified for live delivery.
• Pinned module installations keep their selected version until explicitly changed.
• Custom Bot hosting is restricted to eligible accounts and the supported single-shard application scope.
• Legacy Leveling upload recovery works while the page retains its selected files; a full reload requires selecting them again.
• Change History filters apply to the loaded batch, and older entries without before-and-after data cannot display information they never recorded.

A quick response should mean that the action was received. A success message should mean that it succeeded. We have spent rather a lot of this update making those two sentences agree with the product.

Our rule for this update

The smaller changes, in full

Dashboard, navigation and editing

• Sidebar selection follows the most specific matching page instead of highlighting parent and child together.
• The current sidebar section expands and scrolls into view without a permanent reveal button.
• Locked feature popovers show their explanation once without a redundant disabled toggle.
• Page search includes context for similarly named destinations.
• Server breadcrumbs lead back through the feature to the server overview.
• Long core-tool pages have searchable section navigation.
• Core-tool discovery separates enabled, disabled and attention states.
• Core-tool search supports individual words and shows the result count.
• Active list filters have a clear reset action.
• The overview's completed setup checks can be collapsed.
• Member-directory rows show an explicit search state.
• Personal server counters link to their corresponding view.
• Server favourites have an explicit control.
• Grid or list preference survives another visit.
• Mobile navigation has a labelled Close button with a usable touch target.
• Optional guidance can be collapsed without hiding restrictions.
• Field labels stay visible when the input contains a value.
• Long role and capability descriptions wrap on narrow screens.
• Welcome editors use consistent column widths and insets.
• Role Menu previews no longer place a border against their message text.
• Announcement typing retains focus.
• Selected Announcement members remain clickable atomic chips.
• Fast member-search results no longer miss the open suggestion list.
• Template previews preserve repeated spaces and empty lines.
• Template chips remain atomic after blank paragraphs.
• Single-line paste removes line endings without collapsing surrounding spaces.
• Custom field labels identify the actual editable template surface.
• Leveling prefix inputs preserve typed spaces and commas.
• Shared field labels and hints render through the intended Orbit component.
• Update Center shows the singular unread label for one entry.
• Mobile Update Center removes its duplicate badge and repeated selected title.
• Update Center has a reliable currency display fallback.
• Page transitions respect reduced-motion and low-power preferences.
• Account export illustrations take less space on small screens.
• Public and tool descriptions use shorter, concrete wording.

Loading, login and saved state

• Server search, sorting and filters use bounded pages rather than loading the complete directory.
• A background refresh preserves existing rows.
• New filter requests supersede older results.
• Reopening a saved view does not briefly restore its previous value.
• Query-only navigation avoids unnecessary full-page account loading.
• A failed initial account read offers retry instead of a fabricated account name.
• Transient account-loading errors are distinguished from actual logout.
• Late requests cannot restore an account after logout or an account change.
• Malformed session cookies no longer crash authentication.
• Session expiry follows its actual expiry boundary.
• Login renders Discord before waiting for remote provider discovery.
• Login keeps readable packaged copy during a remote translation outage.
• Missing or disabled translations do not display their technical keys.
• Older locale responses cannot replace the current language.
• Early browser startup failures expose a retry state instead of an endless blank screen.
• The standard login page presents Discord directly without the redundant decorative card.
• Email-free Discord login is supported where the account is explicitly eligible for it.
• Account-link and login continuations preserve the admitted starting site and relative route.
• Protected-action continuations no longer choose a disabled provider merely because it was linked in the past.
• An eligible recent-authentication check covers the same account session for 60 minutes.
• A failed authentication proof does not log out an otherwise valid session.
• Changing a local password clears the corresponding browser session before returning to login.
• Email verification and reset actions reflect actual mail-service availability.
• Public-to-Dashboard navigation loads the correct destination shell.
• Mobile browser asset delivery keeps stylesheet and script compression consistent.

Setup, Welcome and AutoRole

• Setup profile recommendations explain their selected tools.
• Setup shows the effective module selection limit.
• Disabled welcome delivery retains its chosen channel.
• The final setup summary can return to the relevant step for editing.
• Unavailable locales are rejected at setup completion.
• Locked module choices are rechecked before setup is completed.
• Invitation permission groups show selection counts.
• Invitation permissions have a recommended-only filter.
• Permission checkboxes retain their size on narrow screens.
• Channel capability lists include an update time and explicit refresh.
• Administrator permission has a concise explanation in Setup.
• Welcome, direct-message welcome and goodbye messages support text or embeds.
• Welcome message colour controls use the shared picker and input.
• AutoRole no longer skips a manageable join role because the member has a different role above the Bot.
• AutoRole adds independent roles without replacing an outdated complete role list.
• Join-role assignment resumes after Discord membership screening.
• A missing cached server does not permanently suppress join roles.
• Join-role failures are reported instead of silently discarded.

Leveling and Member Profiles

• Pace presets change XP awards and cooldown without rewriting milestone rewards.
• Milestones can contain several add-role and remove-role effects.
• One milestone cannot add and remove the same role.
• Milestone role previews share their sample XP with the member-card preview.
• A zero-XP baseline remains active until the first negative threshold is reached.
• Current members without an XP record can receive the configured zero-XP roles.
• Inactive add-role rewards remove their obsolete assignments.
• Leaving an active remove-role consequence restores the captured membership baseline.
• Disabling Leveling restores the role baseline rather than leaving every consequence applied.
• Leaving and rejoining a server starts a new membership role baseline.
• Later active milestones resolve conflicting role effects consistently.
• Disabled Leveling can show stored XP without presenting inactive rewards as active.
• Custom milestone announcement templates are preserved.
• Historical level placeholders resolve to the configured milestone label.
• Reaching the supported XP boundary produces one milestone announcement rather than repeated announcements.
• Message XP awards no longer fail when saving the cooldown timestamp.
• Quality tests use the unsaved guard settings for short and repetitive samples.
• Tracked role effects can be enumerated for existing-member reconciliation.
• XP corrections prioritise the affected member rather than restarting the entire server scan.
• Role work scheduled during an existing scan is not lost.
• Recorded assignment failures show the unresolved role effect.
• Fallback role information is labelled unverified.
• Member Profiles refresh their role information without interrupting an open editor.
• The public card uses locale-aware signed XP values.
• Leaderboard ties use a consistent rank.
• Leaderboard responses retain the caller's own rank and next-page guidance.
• The retired standalone Level command is not registered alongside the canonical command family.
• The removed challenge-status command does not disable Bonus Challenge earning.
• Editing note content remains limited to its creator.
• Authorised note pinning and deletion retain their separate controls.
• Deleted notes leave normal profile reads.
• The signed self-profile keeps staff notes, private evidence and unrelated actors out of its response.

Forms and Access Requests

• Needs Changes returns the existing response to a new pending review cycle.
• Correction forms prefill the retained answer snapshot.
• Respondents can keep supported attachments while correcting a response.
• Historical answer labels prefer the stored question definition.
• Decision notification preferences belong to the actual approval or rejection.
• Failed decision notifications remain retryable without undoing the decision.
• Reviewer note edits preserve their revision history.
• Pinned reviewer notes can be unpinned explicitly.
• Deleted reviewer notes remain represented in the immutable history.
• Text comparison values can be entered with Enter, comma or field departure.
• Choice equality conditions support several selected values.
• Question-type search includes descriptions and alternative names.
• Changing a question type uses the same searchable selection.
• The role-condition phase selector no longer stacks its label vertically.
• Auto-accept mode hides an irrelevant rejection threshold.
• Disabled Auto Review hides per-question score indicators.
• Manual review roles and expiry hide when review is not selected.
• Question-level legacy role controls are replaced by the phase-aware conditions editor.
• Written month names and common separated date formats are accepted.
• Valid date inputs are normalised consistently in the web form and Discord.
• Response queues keep their status counts without duplicate summary tiles.
• Response capacity information is available in a collapsed section.
• Response identifiers copy an authenticated detail link.
• Known respondent names appear in queues and response details.
• A live refresh keeps the original revision of a dirty settings draft.
• Note-only Access Request events do not trigger role changes.
• Forms-related account notices accept the required server context correctly.

Moderation, AutoMod, Sentinel and Event Logging

• Moderation search and member filters have aligned labels.
• Sort controls sit beside the remaining case filters.
• Long selected filter values stay on one line.
• Case filters use the available width when review controls are absent.
• Reset, refresh and the active-filter count remain reachable.
• Direct moderation links use a clearer status and action layout.
• Absent signed review links do not display redundant link-status text.
• Warnings separate duration inputs from message toggles.
• Disabled member-message options hide their corresponding editor.
• Note deletion and pinning do not grant note-content editing.
• Discord Administrator profile viewing does not grant note or XP mutation permissions.
• A Discord authorisation outage is reported as unavailability rather than a false permission denial.
• AutoMod tabs and sidebar destinations use matching navigation.
• Preset-managed rule edits carry a visible warning.
• Raid rules omit unrelated channel-exception and message-deletion controls.
• Raid help explains the join window and account-age checks.
• Sanction cards explain the required permission and outcome.
• Unavailable AI models do not leave an unusable AI navigation item.
• Disabled AI options retain their saved subordinate values.
• Scam guidance distinguishes text, supported-image and linked-page checks.
• Scam visual-match thresholds are described as similarity rather than misconduct confidence.
• Unsupported or unavailable attachments are not presented as successfully checked.
• Event Logging settings separate events, content, exclusions and retention.
• Event routing lists enabled event families only.
• Event-routing configuration requires a main channel.
• Content-capture help describes its storage consequences beside the setting.
• Sentinel decision explanations keep confidential notes private.
• Public-name-only Sentinel attribution omits the hidden reporter identifiers and profile.
• Authorised subject support remains reachable when ordinary intake is disabled.

Tickets

• The former Ticket Routing page is presented as Settings.
• Open and closed Ticket categories have explicit settings.
• Closing a Ticket can move its channel to the selected closed category.
• Transcript capture can be configured separately from summary delivery.
• Deleting a retained Ticket can publish a transcript summary in the configured channel.
• Transcript summaries link to an authenticated view.
• Captured transcript messages have a separate authorised deletion action.
• The default managed panel-post allowance is three, subject to the effective server limit.
• Lowering the panel-post limit preserves existing placements.
• Panel saves update all managed posts.
• A failed post update does not claim that the saved panel definition was lost.
• Confirmed deleted Discord posts release their exact panel slot.
• Bulk Discord message deletion reconciles matching panel placements.
• Opening placement management can reconcile a previously missed deletion.
• Temporary Discord errors do not release a placement.
• Claim, release and close feedback resolves its labels together.
• A failed welcome send preserves the already-created Ticket channel link.
• Optional audit delivery failure does not invalidate a usable Ticket.
• Ticket templates and statistics refresh after relevant server changes.
• Unsaved Ticket settings retain their draft and original revision during refresh.

Giveaways

• Giveaway links open the current module workspace.
• The private Details view shows the caller's actual entry status.
• Eligibility and chance bonuses are explained in Details.
• Draw verification uses a readable explanation rather than duplicated raw hashes on the public card.
• Entry confirmation no longer waits for the public-card edit.
• Entry counts and personal entry changes remain one consistent result.
• Discord Details messages respect the supported message limits.
• Uncertain Discord edits do not automatically publish a second card.
• An unresolved editor action cannot be submitted again as a new action.
• A successful save remains successful if its optional refresh fails.
• Discard restores the saved Giveaway identity and revision.
• Edited Giveaways load by their identifier independently of list pagination.
• Older drawer responses cannot replace a newly selected record.
• Clearing a date does not produce an invalid editor date.
• Role rewards validate their amount and readiness before submission.
• Winner counts and durations are checked before review.
• Duplicate bonus-role choices are rejected.
• Prize review shows the integrations needed by the selected prize types.
• Image validation accepts the required secure URLs.
• Routine management follows the server's audit-message policy while fairness and fulfilment reasons remain required.

Suggestions and Roadmap

• Public comments use the existing server-controlled discussion setting.
• Long comments fit inside a supported Discord embed.
• Comment delivery does not implicitly parse mentions.
• Private staff notes are excluded from public comment totals.
• Suggestion authors are shown in a rendered attribution field.
• Disabled downvotes and vote removal hide their controls.
• Removing a vote cannot bypass a disabled vote-change policy.
• Merge progress distinguishes unfinished transfers from completed duplicates.
• A merge keeps existing destination votes unchanged.
• A resumed merge continues towards the original target.
• Status changes are blocked while the source is being merged.
• A closed merge destination pauses visibly until reopened.
• Required transition notes are checked before starting a merge.
• Automation summaries count completed transitions rather than attempted ones.
• Self-lists and digests respect Discord message limits.
• Roadmap item limits match the module's supported maximum.
• Cards, status labels and automation confirmations use the server's localisation.

Party Hub

• Room codes keep their existing six-digit format.
• Joining a room no longer waits for artificial reveal animations.
• Late game inputs are rejected against the actual round deadline.
• Speed scores use server receipt timing.
• A submitted slogan cannot be overwritten after submission.
• A submitted vote remains locked.
• A submitted drawing rating remains locked.
• Drawing ratings require an explicit selection instead of submitting a default score.
• Slogan Swindle keeps unrevealed answers out of player-facing options.
• Cooperative Song Line continues after the first correct word.
• Cooperative writer rotation follows the active team.
• Historical song texts include their source attribution.
• Drawing payloads preserve endpoints while simplifying large strokes.
• The drawing toolbar respects the current disabled state.
• Undo and Clear drawing controls have localised accessible names.
• Private image-position previews send the committed choice rather than every pointer movement.
• Image-position drafts reset for each new game.
• The acting player receives the committed game view promptly.
• Host and controller clocks use the same server offset.
• Discord answer controls belong to their exact round.
• Blank and fractional guesses cannot pass an integer-answer game.
• Prediction controls respect disabled modules and unavailable actions.
• Prediction selections expose their pressed state accessibly.

Casino

• Interactive game expiry no longer removes the record before reserved-stake recovery can inspect it.
• Matching player and dealer Blackjack naturals settle as a push.
• A drawn player 21 loses to a dealer natural.
• A player natural is handled separately from a drawn dealer 21.
• Insurance is reported only for a dealer natural.
• Double-down is limited to the initial two-card hand.
• Controls from another game cannot mutate the current session.
• Hold'em does not reveal the turn or river in the initial table view.
• Private-hand inspection does not reveal future community cards.
• Balance-adjustment fields stay separate from account-lock fields.
• Expired account exclusions no longer look like active locks.
• Unavailable module actions remain disabled in management.
• Casino values use locale-aware number formatting.
• Mobile account rows preserve balance and status.
• Balance-adjustment audit context follows server policy and any stricter Casino setting.
• Account locks and game invalidations keep their required safety explanations.

Creator Notifications

• Archive actions use a visible supported icon.
• Active groups are the default view.
• The group archive shows its count.
• Archived sources use a count-bearing disclosure inside each group.
• Archived groups and sources do not consume active capacity.
• Archived sources are excluded from Discord previews.
• Restoring a group starts it paused.
• Restoring configuration rechecks current source limits.
• Permanent-removal confirmations name the exact configuration being removed.
• Groups retained by delivery history explain why archive is their final removal state.
• A delivery that completes during deletion prevents accidental history removal.
• Source moves refresh both affected groups.
• Panel edits update existing live Discord messages.
• Archive transitions finalise the affected live messages.
• YouTube channel URLs and handles resolve through the same account input.
• Invalid provider inputs show localised validation feedback.
• Live and content failures have separate results.
• Monitoring disclosures show the latest supported attempts and errors.
• Unknown live status does not prematurely finish a live message.
• Older videos do not masquerade as newly observed content.
• A failed content check does not hide a successful live check.
• Repeated live-message edits can resume after an earlier failure.
• Creator group and delivery-history details can be collapsed.
• Source-list transitions respect reduced motion.

Modules, Developer Center and API tokens

• Optional integrations do not become automatic module installations.
• An optional inactive integration does not block an unrelated module's activation.
• Store dependency links label optional connections separately.
• Proposed version capabilities are assessed against that proposed version.
• Update review opens before a final operation can be committed.
• Capability acceptance is explicit in the review.
• Reset restores the saved module-update policy.
• Read-only impact reviews do not show an unrelated generic Save bar.
• Unavailable module buttons return a readable unavailable response.
• Recovered module commands are restored on the owning Bot.
• A prepared module is not described as unavailable merely because it has not received its first command.
• Pinned installations retain their selected artifact version.
• Module configuration and restart audit context follows the server's policy.
• Developer enrolment can use the current Orbit profile name.
• Suspension remains effective through developer team membership.
• Invited eligible team members receive the correct Developer Center access state.
• Module access follows current organisation membership.
• Module transfers replace the former personal ownership.
• Lowered team quotas retain existing resources.
• Existing team-member role changes remain possible at member capacity.
• Current Developer Terms acceptance does not approve or unsuspend an application.
• Stale clients cannot accept an unseen agreement version.
• API-token secrets are disclosed only once.
• API-token endpoint selection has descriptions and operation filters.
• Selecting filtered endpoints does not require loading an unbounded catalogue.
• The token catalogue uses 25-row pages.
• Localisation reads are visible in the appropriate account-read scope.
• Activated scoped credentials show the effective account.
• Returning to the personal session clears the delegated view's account state.
• Tokens do not grant access to browser-only security actions.

Permissions and change history

• The permission catalogue and selected detail scroll independently on desktop.
• Narrow permission layouts return to a single document flow.
• Role cards provide larger selectable targets.
• Pending permission differences appear only when a draft changes.
• Reset restores the saved permission mapping without a cloning error.
• Copying another permission's assignments participates in the same draft.
• Individual member exceptions can allow or deny the selected permission.
• Command groups expose their enabled state before advanced rules.
• Disabled command groups are removed from server command registration.
• Channel-policy help explains how category and child-channel rules combine.
• An Allow command rule does not request a denial explanation.
• Deny explanations are labelled optional rule metadata.
• Successful routine changes offer an optional follow-up audit message.
• Supplemental audit text can be edited or cleared with history.
• Required server audit reasons stay in the active form.
• Guild configuration reset accepts its required server context.
• Historical imports preserve an existing audit policy when the older file omits it.
• Change History shows localised action, field and status labels.
• Recorded targets use readable server, case, ticket and tool names.
• Field changes show recorded previous and new values.
• Unknown historical values are not replaced with fabricated comparisons.
• Mobile history cards use the same pagination as the desktop table.
• History retains exact original details in its expandable technical view.
• History filters explain their loaded-batch scope.
• Private staff identities stay out of ordinary server history projections.

Support, feedback, surveys and account data

• Support request types display their eligibility before submission.
• Related-server selection explains an unmet ownership requirement.
• Inactive request types do not offer a misleading submission action.
• Pausing a parent server requirement retains its inactive subordinate settings.
• Support lists and conversations retain the snapshotted request-type name.
• Support creation uses one validated submit action.
• Support fields show required state and character counts.
• Private attachment errors stay beside the attachment control.
• Existing Support conversations remain accessible when new intake is paused.
• Internal notes do not become requester notifications.
• Public reply attribution stays separate from private handling information.
• Ordinary inbox access does not require an unrelated blanket second factor.
• Feedback requester updates preserve paragraph breaks.
• Feedback diagnostics can distinguish operations inside a batched API request.
• Failed feedback rewards reconcile their original currency and amount.
• Opening a scheduled Pulse immediately updates its visible opening time.
• A Pulse with no eligibility rules is explicitly unrestricted.
• Expired Pulse schedules cannot be manually opened.
• Account notices accept server-scoped claims, snoozes and acknowledgements.
• Survey notification settings accept their required server context.
• Personal-data exports retain their temporary archive until private storage consumes it.
• A failed personal-data export does not start the successful-export cooldown.
• Failed export history can be dismissed immediately.
• Completed export history becomes dismissible after one calendar year.
• Dismissal affects the requester's own history entry.
• Exported Custom Bot data excludes operating credentials.
• Custom Bot account deletion removes the current operating credential and disables operation.
• Custom Bot stop and server-assignment release are distinct owner actions.
• Legacy Leveling imports retain successful uploads and retry missing files while the page stays open.
• Upload recovery does not report success until every required file is confirmed.

Public pages and service information

• The Orbit homepage is the root public page.
• The older /orbit-bot address redirects to the homepage.
• The feature hub links to individual feature pages and the setup guide.
• Published articles carry their actual title and excerpt in the readable document.
• Blog and changelog archives support pagination.
• Public editorial feeds expose published entries only.
• Draft, archived, future and missing editorial entries are not public documents.
• Public search links use the primary Orbit origin.
• Private account and server pages remain excluded from public indexing.
• Public sign-in and Dashboard links reflect the available session.
• Legal contents links work without JavaScript.
• Legal section links from earlier editions keep their corresponding destination.
• Legal headings, edition dates and contact details remain readable on narrow screens.
• Developer agreement acceptance names the displayed version.
• The public Health page presents the configured Statusphere views and a link to the full status page.
• An unconfigured public Health page says so rather than inventing service results.
• Optional image inference does not describe healthy text moderation as entirely unavailable.
• Creator-source errors and missing permissions remain explicit instead of appearing as successful empty results.