v3.3.2 — Downloads where your browser saves them

3.3.2 — Downloads where your browser saves them

Files now land where your browser saves its own downloads, collection queues ride out Nexus outages and background restarts, large Wabbajack modlists are read without freezing the page, and the same error from Chrome, Edge or Firefox is reported once. Both browser ZIPs are under Assets.

• Your browser's download folder (#34): new installs leave Browser download folder empty, so each file goes where your browser saves its own downloads, and Ask where to save each file opens the folder you picked last. On Opera, a file placed in a folder set here goes to the system Downloads folder whatever Opera's own location is; the folder field and the setup page now say so on Opera. A full path such as D:\mods no longer becomes a D mods folder, for single files or collections: choose it as your browser's download location instead. Existing settings are kept, so on Opera with your own download location, clear the field once.
• Collection queues that keep going: a Nexus outage or a request that times out is waited out on the same file instead of failing the rest of the collection. If the browser stops the extension's background worker just as a file starts, the restarted worker takes over that download (only one this extension started, from the same host) instead of saving a second copy.
• History, rate limits and .meta files: importing files into a collection's history while it downloads no longer loses a file the queue just recorded; a rate limit met in one tab can no longer shorten a longer wait the queue already has; a small single file that finishes at once still gets its Mod Organizer 2 .meta.
• Large Wabbajack modlists: the modlist is streamed in 1 MiB pieces with a running checksum instead of being loaded whole and copied twice, and the page stays responsive while hundreds of megabytes are read. Escaped characters in names, game names in any case and modlist names in Greek, Japanese or other scripts are handled, and the import summary says what was not queued and why.
• Narrow windows and phones: Select mods shows each mod on two readable lines below 560 px, and the report page's controls are touch-sized.
• Clearer error reports: a fault is grouped by the function it happened in, the same way from every browser, and errors on the extension's own pages are now recorded too. An error message containing a NUL character no longer gets an automatic report refused and deleted.

Repository & reports — diagnostics and deployment

• The private diagnostics dashboard shows Chrome Web Store and Google Analytics 4 listing figures, notifies about new store reviews, lists open GitHub issues and recent Discussions, keeps copies of automatic reports sent through the Discord path, and has a compact iPhone layout with docked tabs.
• Reports now carry the function a fault happened in, so existing dashboard issues are grouped afresh once. The relay and diagnostics Workers must both run this version; pushes to main deploy them once their checks pass and the repository's Cloudflare token is set. The relay baseline is 3.3.2.
• Development dependencies: Miniflare's undici is 7.30.1, and the Firefox package check calls addons-linter directly. Extension permissions are unchanged, and no new telemetry is sent.

Release checks: publication runs ESLint, extension regressions and browser-package validation, Firefox package lint, extension Playwright tests (now including 320, 390 and 430 px layouts), diagnostics TypeScript and regression tests, mobile PWA browser tests and a Cloudflare Worker dry-run build. Opera itself was not available for testing; its fix is verified through the download request the extension makes.