Orion

Auto-complete every Discord Quest in seconds — v4.9.7

Completes all Discord Quests automatically — game, video, stream, activity, and achievement quests. Paste one script into DevTools, get every reward. No installs, no tokens, no dependencies.

Works on every Discord update — no hardcoded paths, uses constructor.displayName for resilient module detection.

Get Started • How It Works • Configuration

Caution

Discord is actively cracking down on quest automation (April 2026+). Some users have received system messages flagging their accounts after running automation tools (any tool, not just this one). The risk is real now, and enforcement can hit the entire Discord account, not only quest rewards. Use at your own discretion. Honest trade-off: faster Orbs vs a non-zero chance of an account strike.

The ACHIEVEMENT_IN_ACTIVITY bypass does more than spoof progress. To complete those quests it runs a real OAuth2 authorization against the quest's application (scopes identify applications.commands applications.entitlements), mints a proxy ticket, posts forged progress to the activity backend at discordsays.com, then revokes the authorization it created. Full flow: authorize -> proxy ticket -> discordsays authorize -> discordsays progress -> revoke. It is forging quest progress on a logged-in account, which is exactly what Discord is enforcing against. If you don't want that on your main account, don't run it there. Orion asks for explicit confirmation before each app authorization (the userscript shows a popup; the Vencord plugin keeps it behind an off-by-default setting), and the only data sent to discordsays.com is that app's OAuth code, the proxy ticket, and the target progress count — never your Discord token, email, or password.

Warning

Vanilla Discord Stable is partially incompatible. A recent Stable build changed the webpack runtime so webpackChunkdiscord_app.push no longer exposes the live module cache post-boot.

Workarounds (any of these works on Stable):

1. Paste the userscript with Vencord installed — Orion v4.6+ auto-detects Vencord and uses its boot-time-injected Webpack API to restore full functionality.
2. Install the OrionQuests Vencord userplugin — no console pasting, runs at Discord boot, exposes /orion start|stop|status slash commands. Best long-term option for Stable users. If you use nin0's UserpluginInstaller, paste https://github.com/nyxxbit/discord-quest-completer into its Install Plugin field and it installs and self-updates from there.
3. Or use Discord Canary (vanilla, no mods), where the native userscript extraction still works.

Why Orion?

• Covers all 5 quest types — PLAY, STREAM, VIDEO, ACTIVITY, and ACHIEVEMENT_IN_ACTIVITY. Most other tools only handle PLAY (game-time) quests.
• Userscript and Vencord plugin in one repo — pick whichever fits your setup. Both share the same engine, both kept in sync.
• Auto-claiming — Claim rewards directly from the dashboard. Tries to claim automatically (if enabled), or provides a smart interactive button if captcha is needed.
• Resilient module loader — finds Discord stores by class name, not minified paths. Dual extraction path (Vencord API + native fallback) survives Discord webpack changes.
• Smart rate limiting — exponential backoff on 429/5xx, skip-list for dead quests, randomized polling intervals. Distinguishes between global and endpoint limits, non-blocking retries.
• Fault-tolerant execution — One failed quest won't break the queue (Promise.allSettled).
• Zero setup — single paste into the console. No Node.js, no npm, no extensions.

Quick start

Important

Partial Browser/Mobile Support. Orion runs in Discord web version or on mobile browsers Discord (via script-injection extensions like Kiwi Browser) for web-compatible quests (e.g., Video, Activity). However, GAME and STREAM quests are automatically filtered out as they are impossible outside the Discord Desktop client.

1. Open Discord (Canary recommended — console enabled by default)

2. Press Ctrl + Shift + I → Console tab

3. Paste index.js and hit Enter

Shift + . toggles the dashboard. Click STOP to kill it instantly.

{ "DANGEROUS_ENABLE_DEVTOOLS_ONLY_ENABLE_IF_YOU_KNOW_WHAT_YOURE_DOING": true }

How it works

Orion extracts Discord's internal webpack stores (QuestStore, RunStore, Dispatcher, etc.) and uses them to spoof game processes, send fake video progress, and dispatch heartbeat signals — all through Discord's own authenticated API client.

QuestStore → filter incomplete → JIT enroll → dispatch tasks → poll progress → auto-claim → done

Dashboard

Draggable overlay styled to match native Discord design. Live-sorts tasks so you always see what matters:

Desktop notifications fire on each quest completion.

Auto & In-UI Claiming

You can configure Orion's claiming behavior via the TRY_TO_CLAIM_REWARD setting.

• Automated Claiming: If enabled, tries to claim instantly upon completion.
• In-UI Button: If auto-claim fails due to captcha, or is disabled, a CLAIM REWARD button appears directly on the task card.

Configuration

Most settings are now configurable through the quest picker UI that appears before the script starts:

• Reward filters — Toggle quests by reward type (Orbs, Avatar Decorations, In-Game Items)
• Quest checkboxes — Select/deselect individual quests
• Auto-enroll — Automatically accept quests before running them (default: ON)
• Auto-claim — Attempt to claim rewards on completion (default: OFF to avoid captcha)

Advanced settings can still be tweaked in the CONFIG object before pasting:

const CONFIG = {
    HIDE_ACTIVITY: false,        // suppress "Playing..." from friends list
    MAX_LOG_ITEMS: 60,           // UI log limit
};

Error handling

Architecture

Single-file IIFE. No build tools, no external deps.

index.js
├─ CONFIG / SYS / RUNTIME      tunables, frozen system limits, active cleanups
├─ ErrorHandler                classifies HTTP errors (retry / skip / fatal)
├─ Logger                      DOM dashboard + task state + log output
├─ Traffic                     FIFO request queue with exponential backoff
├─ Patcher                     RunStore / StreamStore monkey-patching
├─ Tasks                       VIDEO, GAME, STREAM, ACTIVITY, ACHIEVEMENT handlers
├─ loadModules()               dual-path extraction (Vencord API + native fallback)
└─ main()                      discover → JIT enroll → execute → claim → loop

Module detection

Unlike other scripts that break on every Discord update, Orion finds stores by their class name (QuestStore, RunningGameStore, etc.) via constructor.displayName. The Dispatcher is found by structural signature (_subscriptions + subscribe + dispatch), and the API client by its unique .del method. No hardcoded minified paths.

For a full internal tour of the script, see docs/ARCHITECTURE.md.

Alternatives

Orion isn't the only tool in this space. If our approach doesn't fit your setup, these projects might:

• markterence/discord-quest-completer — Native Windows app (Tauri/Rust + Vue). Creates dummy game executables that satisfy Discord's process detection without injecting into the client at all. Most resilient long-term because it doesn't depend on Discord internals. Trade-off: PLAY quests only (no VIDEO/STREAM/ACTIVITY/ACHIEVEMENT support), Windows-only, requires WebView2.
• nicola02nb/completeDiscordQuest — Vencord plugin (also a BetterDiscord port available). Smaller and simpler than ours, port of aamiaa's original snippet that started this whole space. Mature (online since Sep 2025).
• nvckai/Discord-Web-Auto-Quest-Extension — Chrome extension. One-click install but VIDEO-focused.

Why Orion if these exist:

• We're the only tool covering all 5 quest types with one codebase.
• Userscript + Vencord plugin share the same engine in this repo, so behavior matches across install paths.
• Active development (multiple releases per month, community PRs merged on the same day they land).

Honest disclosure: we depend on Discord's webpack/internals. Every Discord update has a chance of breaking us. markterence's process-injection approach is structurally less brittle for users who only need PLAY quests.

Contributing

Contributions are welcome — bug reports, PRs, and docs. Start with CONTRIBUTING.md for the checklist and code style. Use the issue templates when reporting bugs or requesting features.

Changelog

v4.9.7

• The repo installs as a Vencord userplugin now — paste https://github.com/nyxxbit/discord-quest-completer into nin0's UserpluginInstaller and it clones, builds and self-updates from there, no manual clone or file copying (#42). That installer does a plain git clone into src/userplugins, and Vencord's build only reads index.ts(x) and native.ts from the top level of a plugin folder, so the plugin sources had to move out of vencord-plugin/ and up to the repo root; a subdirectory layout cannot work with either. vencord-plugin/README.md moved to docs/VENCORD-PLUGIN.md. The userscript keeps its path and its raw URL and is not part of the plugin build — both esbuild and the installer resolve index.tsx ahead of index.js. A CI job now clones Vencord, checks this repo out the way the installer would, builds, and asserts the plugin reached the renderer and main-process bundles with the slash command registered and no userscript leakage; it builds against Vencord's default branch weekly, so an upstream change that breaks the plugin shows up there instead of in a bug report. The quest engine itself is unchanged this release.

v4.9.6

• Fix: game quests never progressed — Discord's taskConfigV2 moved the application off the quest config and onto each task (tasks.PLAY_ON_DESKTOP.applications[0].id); config.application.id no longer exists, so every game/stream quest fell through to a ?? 0 fallback and injected a process claiming to be application 0. Discord could never match that to the quest, so it never sent a single heartbeat and the quest sat at 0% (#43). This hit Canary first and has since reached Stable. Canary also derives quest eligibility from getVisibleGame / getVisibleRunningGames / getRunningDiscordApplicationIds / getCandidateGames, which the old patch left empty — all four are now patched when present and restored on cleanup. Two things had been hiding the failure: the dashboard ticker incremented progress locally every second regardless of heartbeats, so a quest earning nothing still showed a bar climbing to 100%, and nothing failed until the 25-minute timer. The ticker now extrapolates only from the last real heartbeat, so it can't run past what Discord reported, and a game/stream task with no heartbeat inside 90s aborts with a clear message. Progress also reads the task key detected from the config instead of a hardcoded PLAY_ON_DESKTOP (so PLAY_ON_DESKTOP_V2 resolves) and seeds from the server's stored value on start. The legacy config.application.id path remains as a fallback for clients that haven't picked up the change yet.
• Fix: the achievement bypass was dead for the same reason — bypassAchievement still read config.application.id directly and returned early when it resolved to nothing, so every ACHIEVEMENT_IN_ACTIVITY quest fell straight through to "Cannot auto-complete" without ever attempting the Discord Says flow. It now uses the application id already resolved for the task, keeping the legacy read as a fallback and the numeric guard unchanged. Verified end to end against live quests on both engines: the userscript completes the quest through the localhost relay, the Vencord plugin through its native module, and in both cases the temporary OAuth grant is revoked afterwards while pre-existing authorizations are left untouched.
• Fix: a game/stream quest that stalled after its first heartbeat still idled for 25 minutes — the no-heartbeat watchdog only checked once, so it caught a quest that never started but not one that stopped partway. It is now re-armed on every heartbeat and reports which case it hit.
• Fix (plugin): quests skipped for a missing application id were re-announced every cycle — the skip was recorded in a set that nothing reads, so the same quest was re-detected and re-logged every few seconds. It now goes into the set activeQuests() actually filters on.

v4.9.5

• Fix: the Vencord installer bundle no longer breaks Vencord's updater — The bundle was shipping a build compiled in git-updater mode (Standalone: false) into %APPDATA%\Vencord, which has no git repo, so Vencord threw not a git repository every launch and showed "can't check for updates" (#39). The plugin was never the cause; it was the build flags. The bundle is now built --standalone --disable-updater, which turns the updater off cleanly (no error, and no risk of the standalone HTTP updater silently reverting the dist to vanilla and deleting the plugin). Honest tradeoff, now documented: Vencord is frozen at the bundled version; to get updates back, reinstall official Vencord and re-run the installer. INSTALL.cmd now backs up your existing Vencord build to dist.orion-backup first so it's undoable. Userscript and plugin source are unchanged this release; only the installer bundle differs. Root cause was pinned by a senior review panel that read the Vencord updater internals.

v4.9.4

• Deeper security pass on the ACHIEVEMENT bypass — A multi-angle audit following #38 surfaced more to address. The bypass now requires explicit consent before authorizing any app: the userscript shows a popup with the app name, the OAuth scopes, and a note that it revokes right after (defaults to decline, so an idle prompt never authorizes); the Vencord plugin gates it behind an off-by-default setting. A failed grant snapshot now aborts before authorizing instead of authorizing without a way to revoke. redirect: "error" on every discordsays.com fetch (userscript and native module) so a 3xx can't bounce the auth token to another host. The native module validates the questId and Referer, not only the appId. The relay reflects CORS only to Discord origins, drops non-allowlisted headers, caps the body size, and checks the Host. Also fixed a stored-DOM-injection bug — a crafted quest or reward name could inject markup into the dashboard; all server-controlled strings are now escaped. Plus assorted hardening: guarded JSON parsing of activity responses, NaN-safe quest expiry, and listener/audio/shutdown leak fixes. docs/ARCHITECTURE.md rewritten to match the current engine.

v4.9.3

• Security hardening of the ACHIEVEMENT bypass — From a detailed security report (#38). The OAuth grant cleanup now runs in a finally block, so a failed bypass never leaves the quest's app authorized on your account, and it only revokes the grant Orion created (diffed against a pre-flow snapshot of your existing grants) so it won't touch an authorization that already existed before the run. The localhost relay no longer follows redirects and rejects any host or path outside the two discordsays.com endpoints it needs. The userscript and the Vencord native module both validate the application id is numeric before building any URL (closes the SSRF angle). The README now spells out the full OAuth lifecycle and the account-level ban risk. The non-tech installer bundle is English-only now (INSTALL.cmd).

v4.9.2

• Cleaner picker when the options panel is open — Clicking the gear now hides the quest list and the START/DESELECT buttons while the options are showing, so the panel isn't buried under a long quest list. Click the gear again to bring them back. Minor CSS spacing fixes too. Thanks to @TirOFlanc in #37.

v4.9.1

• Fix: Vencord plugin skipped GAME/STREAM quests on desktop — The plugin detected "desktop" by probing window.DiscordNative, which isn't reliably visible from the plugin's execution context. Game quests were wrongly skipped with requires desktop app. Skipping. even on Discord Desktop, while the userscript handled them fine. Switched to Vencord's build-time IS_DISCORD_DESKTOP / IS_VESKTOP globals. Resolves #35.

v4.9

• ACHIEVEMENT_IN_ACTIVITY auto-bypass works on stock Discord Desktop — no Vencord, no BetterDiscord, no client mod. The trick is a tiny localhost HTTP relay (tools/orion-relay/) that the userscript probes on boot. Discord's CSP allows connect-src http://127.0.0.1:* (for RPC with games); the relay forwards POSTs to *.discordsays.com from outside the browser sandbox. One PowerShell script + one .cmd launcher, ~100 lines total. Download from the release page, double-click to start, leave the window open, paste the userscript. Done.
• Transport picker priority — _bypassPost now tries (1) Orion Relay on 127.0.0.1:43210, (2) Vencord plugin via VencordNative.pluginHelpers.OrionQuests, (3) DiscordNative HTTP probes (best-effort for future Discord builds), (4) direct fetch (web Discord). First hit wins.

v4.8.2

• Userscript hands off discordsays POSTs to the Vencord plugin when installed — New _bypassPost transport picker. On Discord Desktop with Vencord + OrionQuests plugin installed, the userscript console script now detects VencordNative.pluginHelpers.OrionQuests and routes the CSP-blocked POSTs through the plugin's native module instead of failing. So ACHIEVEMENT_IN_ACTIVITY auto-completes from the standalone userscript too, as long as the Vencord plugin is also installed. Also probes DiscordNative.http, DiscordNative.fileManager.fetchURL, and a few sibling paths as a best-effort fallback in case a future Discord build exposes generic HTTP. On web Discord (no Vencord, no CSP), direct fetch works.

v4.8.1

• Honest CSP error message + Vencord native bypass — Testing v4.8 surfaced that Discord's renderer CSP (connect-src allowlist) blocks the final fetch() to *.discordsays.com from the userscript. Steps 1-2 of the bypass (OAuth2 authorize + proxy-ticket mint) work; step 3 (POST to the activity backend) does not. The userscript now detects the CSP failure and prints a clear message pointing to the Vencord plugin instead of "Failed to fetch". The Vencord plugin port gained a native module (native.ts) that runs the discordsays POSTs in the Electron main process where CSP doesn't apply — confirmed working in production against real ACHIEVEMENT_IN_ACTIVITY quests.

v4.8

• ACHIEVEMENT_IN_ACTIVITY auto-bypass — New OAuth2 → discordsays.com handshake. When Discord's heartbeat endpoint rejects (HTTP 403, which it does for most current Achievement quests), Orion now authorizes against the activity's own backend, mints a proxy ticket, and POSTs the target progress directly. No more 25-minute passive wait, no more "join the activity manually". The previous picker toggle to skip these is now mandatory behavior — if both paths fail (typically age-gated or delisted activities like The Odyssey), the quest is skipped cleanly instead of blocking a queue slot. Note: the discordsays.com POSTs are blocked by Discord's renderer CSP — the userscript can only complete the OAuth handshake locally. See v4.8.1 for the workaround.
• 2x faster video polling — Video heartbeats now run at 3.5-4.75s instead of 7-9.5s. Cuts each video quest's wall-clock in half. Discord's server-side validation accepts the faster cadence.
• Two parallel video quests — Video concurrency raised from 1 to 2. Two video quests complete simultaneously instead of serially.
• Fix TypeError: Cannot read properties of null on gear-icon click — The options gear stays mounted in the header after the picker closes, but its panel doesn't. Added a null guard so post-picker clicks no longer throw.

v4.7

• Collapse-on-double-click + drag boundaries — Double-click the header to minimize the panel to a 50px stub; double-click again to expand. The dashboard can no longer be dragged outside the viewport on either axis. Picker options panel hidden behind a new gear icon (⚙️) for a cleaner first-paint. Thanks to @TirOFlanc in #32.
• Skip manual activities — New picker toggle. When ACHIEVEMENT_IN_ACTIVITY quests fall back to passive mode (waiting for you to actually play the activity), the script now optionally fail-fast skips them so the queue keeps moving instead of blocking a slot for 25 minutes. Default off. Resolves #33.
• Random 1-30min delay between cycles — New picker toggle. Injects a randomized idle gap between quest cycles for anti-detection during long AFK runs. Default off (preserves current behavior). Implements the request in #30.
• Dashboard persists when rewards are unclaimed — The widget no longer auto-shuts down the moment the last quest completes if any task still has a CLAIM button waiting. Click STOP manually after claiming. Resolves #31.

v4.6.3

• Fix CSP violation in credit text — The header's by syntt_ was an <a> with inline onmouseover / onmouseout handlers. Discord enforces strict CSP and rejected the inline handlers with a console error; the link itself also redirected to /@me (Discord's URL scheme does not open user profiles via discord.com/users/<id>). Replaced with a plain <span class="dev-credit"> and moved styling into the stylesheet. Resolves #29.

v4.6.2

• Native UI overhaul — Replaced hardcoded hex colors with Discord's native CSS variables. The widget now automatically adapts to Light, Dark, AMOLED, and custom themes.
• Circular progress & decluttering — Switched linear progress bars to circular indicators (hover to see exact percentages). Completed quests now hide unnecessary text to keep the interface clean.
• Desktop environment guard — The script now checks for window.DiscordNative. Game and Stream quests are automatically hidden and skipped if you run the script in a web browser.
• Removed window position saving — Dropped localStorage usage for tracking the widget's coordinates to fix console spam and window.localStorage is undefined errors on newer Discord builds where storage access is restricted.
• Optimistic UI & under-the-hood fixes — Added a local ticker for smooth visual progress updates.

v4.6.1

• Louder completion sound — Bumped the gain on the quest-completion ping (0.12 → 0.45) and arpeggio (0.18 → 0.55). Headphone users were complaining the tone was inaudible.

v4.6

• Vencord integration — loadModules now uses window.Vencord.Webpack directly when Vencord is installed. Restores full functionality on modern Discord Stable, where the native chunk push hook can no longer reach the live module cache. Resolves #20
• Sentry-proof native extraction — The push callback fires once per registered runtime; Discord ships Sentry's stripped runtime alongside the real one. The capture now picks the require with the largest .c, ignoring Sentry's tiny instance. Resolves #23 and #26
• Sound on completion — New picker toggle plays a soft tone after each quest finishes and a 3-note arpeggio when the whole queue is done. Useful with auto-claim off so you can come back before the captcha times out. Resolves #24

v4.5.5

• Hotfix Canary regression from v4.5.4 — first attempt at the dual-capture path. Superseded by v4.6's Sentry-proof solution.

v4.5.4 (broken on Canary — use v4.5.5+)

• Resilient loadModules — __webpack_require__ is now captured via the chunk callback closure instead of relying on push()'s return value. Some Discord builds return undefined from push; the callback always fires with the require argument
• CSS :disabled styling — Claim button disabled/failed states are driven by :disabled and a .failed modifier class. No more inline-style assignments scattered across handler code
• Filter handler dedup — The reward-filter and type-filter click handlers were near-identical; now collapsed into a single FILTER_KINDS table-driven path
• Icon resolution simplification — 7-arm if/else chain in Logger.render replaced with a single ternary expression

v4.5.3

• Pending state — Unenrolled quests now wait for manual acceptance in Discord instead of failing when auto-enroll is disabled.
• Ghost-task fix — Unenrolled and hidden quests no longer attempt execution or time out in the background.
• Claim button lock — Prevented API spam and visual state resets by locking the "Claim Reward" button during UI renders.
• Picker refactor — Moved UI logic inside Logger and switched to native HTML forms for resilient state collection.
• Dynamic filters — Added Quest Type filtering.

v4.5.2

• Fix NodeList error — $$ now returns a real Array so .every() works on visible quest cards. Resolves TypeError: visible.every is not a function when clicking (De)select All

v4.5.1

• Fix (De)select All — The toggle button now correctly checks/unchecks visible quest checkboxes without hiding them. Reward filters remain independent. Button label syncs with actual checkbox state

v4.5

• Quest picker UI — Script no longer starts immediately. A visual quest picker shows all available quests with checkboxes, color-coded by reward type (Orbs, Avatar Decorations, In-Game Items). Filter entire reward categories with one click, select/deselect individual quests, then hit START
• Options panel — Toggle auto-enroll and auto-claim directly from the picker UI before starting. No more editing CONFIG to control these behaviors
• Reward type filters — Pill buttons at the top let you enable/disable entire reward categories. Disabling "Orbs" hides and unchecks all Orb quests instantly

v4.4

• JIT enrollment — Quests enroll one at a time right before execution instead of in bulk, eliminating mass-enrollment detection vectors
• Natural video polling — Replaced static 1s intervals with 7–9.5s polling using 6-decimal float timestamps that match native Chromium player behavior
• Randomized delays — All fixed-interval API calls now use randomized timing ranges to break predictable patterns
• Correct Windows PIDs — Fake game process IDs generated as multiples of 4 to comply with Windows NT kernel architecture
• Sequential execution — Both game and video tasks now run sequentially (concurrency = 1) to avoid parallel request spikes
• Proper cleanup — Removes #orion-styles element on shutdown, debug logging for previously silent catch blocks

v4.3

• GO TO QUESTS button — Achievement quests in RUNNING state now show an ACTION REQUIRED status with a navigation button that uses Discord's native router (transitionTo('/quest-home')) to jump straight to the quest page
• Resilient router detection — New findRouter() locates Discord's minified transitionTo by source signature ("transitionTo -"), no hardcoded paths
• Standardized log tags — Unified prefixes across the codebase ([System], [Network], [Task], [Cycle], [Enroll], [Claim]) for consistent, readable output
• Cleaner UI logs — debug level messages now go to DevTools only and no longer spam the in-app dashboard
• Achievement progress display — Progress text now omits the s (seconds) suffix for ACHIEVEMENT quests since their target is a count, not a duration
• Fixed progress text updates — Restored missing progress-text class so live progress numbers update correctly on task cards

v4.2

• Native UI Claiming: Added in-UI claiming via Claim Reward button.
• Rigid Configuration: Moved hardcoded system limits to a frozen SYS object and added TRY_TO_CLAIM_REWARD config.
• Fault-Tolerant Concurrency: Switched to Promise.allSettled to prevent queue crashes on a single task failure.
• Strict Garbage Collection: Added RUNTIME.cleanups to track and safely flush active event listeners on script stop.
• RPC & Lock Failsafes: Forces dummy PID 9999 to reliably clear "Playing" status, and releases window.orionLock on fatal errors.
• Granular Rate Limiting: Differentiates between global (queue-freezing) and endpoint-specific API limits.

v4.1

• Resilient loadModules() — uses constructor.displayName instead of hardcoded .A/.Z/.Ay/.ZP paths
• Auto-claim rewards (optimistic POST + captcha fallback with CLAIM button)
• Adaptive video speed (6-22 API calls instead of 180 for 900s quests)
• ACHIEVEMENT_IN_ACTIVITY handler for milestone-based quests
• WATCH_VIDEO_ON_MOBILE progress tracking fix
• Task sorting by progress percentage
• Per-cycle try-catch for crash isolation
• Fixed scroll (After activating the script, it turned blue when hovered)

v4.0

• Fixed Issue #5: enrollment 404 no longer crashes the script
• ErrorHandler module with retry/skip/fatal classification
• Traffic queue with exponential backoff for 5xx errors
• Skip-list for permanently failed quests
• Idempotent cleanup in GAME/STREAM handlers

Disclaimer

This tool is for educational and research purposes only. Automating user actions violates Discord's Terms of Service. The developer is not responsible for any account suspensions or bans. Use at your own risk.

Built by syntt_

If this helped you, drop a star — it keeps the project alive.