v2.2.0

v2.2.0 — 2026-10-07

Fixes for both reported problems, the six community pull requests, and a round of reliability work
on top of them. Thanks to @thibaup and @sjschillinger for their pull requests.

Using a master password with 2.0? 2.0 never opens after its password prompt, so updating from
the update window that appears over that prompt is the way to go. When 2.2 then starts for the first
time it may ask for your master password once more, to restore your accounts from the backup 2.0 left
behind.

Fixed

• Unlocking with a master password works again (#7). In 2.0 the unlock prompt disappeared after
  any password, right or wrong, and the manager never opened. A wrong password is now shown in the
  prompt and you can try again.
• Updating over the unlock prompt can no longer empty your account list. In 2.0, "Update now" in
  the update window that opened over the unlock prompt saved the account file before it was read.
  The update check now starts after unlocking, an account file that was never read is never saved,
  and 2.2 offers to restore accounts that 2.0 emptied this way.
• Browser sign-in no longer says the window was closed while it is still open (#8). Sign-in
  followed the process that was started first, which a browser can hand its window to another
  process and exit (it does that, for example, when the manager runs as administrator). Whether the
  window is open now comes from the browser itself, closing it is reported as closed, Stop works at
  any moment, and the sign-in never sees the login page's network traffic.
• The password tab no longer claims a captcha you never saw. When Roblox wants to check a
  sign-in on its own page, the dialog switches to the browser tab and says so.
• Close, minimize, auto-close, the RAM limit and Anti-AFK only act on the Roblox client the manager
  tracked. A process id Windows reused for another program or another account's client can no
  longer be closed or typed into by mistake, and two launches at the same moment no longer claim the
  same client (#1, #2).
• Launches no longer race. Every launch — launch bar, presets, schedules, the watchdog, the local
  API — waits for the previous client to appear before it starts, so clients are never attributed to
  the wrong account and one launch's graphics profile can't replace another's.
• A schedule's auto-close closes exactly the clients that schedule started, including one the
  watchdog relaunched after a crash, never a client you started yourself (#4).
• Private servers in presets. A private-server link pasted into a preset's "Server ID" box was
  launched as a Job ID and failed. Presets now have a destination (game, server, private server,
  join player); presets from 2.0 are converted once, including links typed into the old box. A
  preset switched back to "Game" stays a game preset.
• Auto-rejoin returns to the same destination. A client that crashed in a private server or while
  following a player used to rejoin a public server of the place. A public server that fails twice is
  swapped for any server of the place, and a failed relaunch is retried twice.
• An older account save can no longer overwrite a newer one (#3).
• Pasting a game link into a Place ID box no longer turns the rest of the link into part of the place
  number, also for --launch on the command line.
• Launch errors no longer echo the launch link, which carries a one-time sign-in ticket.
• Playtime counts clients while they run, and sorting accounts by playtime works.
• Starting the exe a second time no longer wipes the playtime history, and it brings the running
  window back (also from the tray).
• "Close all" and scheduled close tasks also cancel rejoins that were waiting, so nothing comes back
  on its own afterwards.
• A cookie for an account you already have counts as added, a 2FA secret with a typo shows no code
  instead of a wrong one, and clearing a copied secret is retried while another program holds the
  clipboard (#5).
• Changing the language no longer resets a preset's performance profile.
• "Lock when hidden to the tray" now also locks when the manager starts minimized with Windows.

Added

• Join player and private server destinations for presets, with the player looked up while
  you type.
• Ultra-low AFK performance profile per preset: FPS cap (15 by default), lowest graphics, optional
  minimize once the client is in game (Roblox stops loading while minimized). Every part can be
  switched off in Settings → Graphics. The next launch without it restores your normal settings,
  also if a client with the profile was still running.
• Random Anti-AFK timing. Each client gets its own schedule, optionally random between two
  intervals, so several clients aren't focused at the same second. The overview shows when each
  client gets its next key press and how often it was rejoined.
• Batch launches wait for each client before starting the next account, plus an optional random
  extra delay per preset. A failed account doesn't stop the rest; the result reads "5 launched,
  1 failed". A Stop button ends a running batch before the next account.
• Auto-rejoin no longer gives up. It used to stop after 3 rejoins within 10 minutes. Now the first
  rejoins in a row are immediate and later ones wait longer (2, 5, 10, then 15 minutes), for as long
  as rejoin is on. A waiting rejoin is shown on the overview with a Stop button, and a client that
  ran for 10 minutes resets the count.
• Saved places remember their server. The launch bar's bookmark saves the Job ID or
  private-server / share link with the place (encrypted), and presets can use a saved place, so a
  link is pasted once and several presets can share it. With Hide usernames on, the launch bar
  shows a saved, remembered or just used private-server link as a placeholder.
• Rejoin after a disconnect (optional): a client whose account stops showing as in game — a
  network drop that leaves it on an error screen — is closed and rejoined. It only acts on presence
  Roblox just reported, and stops after three restarts in a row that never got into a game.
• Restart clients regularly (optional): each client is relaunched after a set time, one at a time,
  into the same game and server type, with the same retries as crash recovery.
• The manager's own memory use is shown under Settings → Diagnostics and in the copied report.
• Test the browser under Settings → Browser, Copy report under Settings → Diagnostics (with
  cookies, tokens, webhooks, private-server codes and sign-in tickets removed), and Minimize per
  client.
• Local API: /launch takes link= or followUserId=; new /preset?name= (409 while that preset is
  already launching).
• Unit tests for the logic that has no UI (destinations, link parsing, preset migration, timing,
  recovery, redaction, the data folder), run before every release.

Changed

• If the data folder next to the exe can't be written to, the manager moves to the per-user folder,
  brings the data along (checked, never overwriting anything; the old folder is left untouched) and
  stays there from then on.
• The memory settings say what they do: the RAM threshold force-closes a client (it is not a memory
  limit), and trimming frees memory only until the client needs it again. Auto-trim runs at most
  every 5 minutes.
• A second batch from the launch bar, or a preset that is already launching, is refused instead of
  running twice.

---

Download: RobloxAccountManager.exe (56.5 MB) — one portable file, nothing to install.

RobloxAccountManager.exe SHA-256: 9decf36150fe896eb17da5c8c881546f977aad53b551974ee1a05a5fccae60af

The in-app updater verifies this checksum before it replaces anything, and keeps your previous version so you can roll back from Settings -> Updates.

v2.0.0

v2.0.0 — 2026-09-17

Rebuilt from the ground up: a new interface, eight languages, and every feature that was still open
on the roadmap.

A new interface

• New layout. A sidebar with your groups, an Overview page, and an Accounts page with a
  detail panel next to the list. Everything about an account (launching, notes, session, 2FA, proxy,
  FastFlags) is in that panel, in tabs.
• Light, dark or system theme with six accent colors. The color editor is still there for
  fine-tuning.
• Command palette. Press Ctrl+K to jump to any account, page or setting, or run an action.
• Settings in categories with a search box, instead of one long page.
• Eight languages: English, Deutsch, Español, Français, Português (Brasil), Polski, Türkçe and
  Русский. The app starts in your Windows language; change it under Settings → General.
• Better filtering and sorting. Filter by online, in game, offline, needs attention or pinned;
  sort by name, status, last used, Robux or playtime; switch between a comfortable and a compact list.
• Keyboard shortcuts throughout: Ctrl+N add account, Ctrl+F search, Enter launch,
  Space tick, F5 refresh, Ctrl+1–5 switch pages.

Roadmap features

• Account health. The Overview lists sessions that have expired, haven't been checked for two
  weeks or are over a year old, with a one-click check or sign-in. Every account shows its session
  age and when it was last checked.
• Presets and schedules editor. The new Automation page builds launch presets (accounts,
  place, delay) and schedules (time, days, launch or close, close again after a while) without
  touching a file.
• Per-account proxy is now actually used: Roblox web requests and browser windows for that
  account go through it. Each account has its own Test button.
• Light mode, as a proper theme rather than an edited dark one.

Signing in

• Browser sign-in is the default. Roblox's own login page opens in a clean, temporary profile of
  Edge or Chrome. Captchas, 2-step verification and passkeys work as usual, the password never
  passes through the app, and the profile is deleted right after.
• The private browser download is optional now. It is only needed on PCs without Edge or Chrome,
  and every download is checked against the SHA-256 published with it.
• Signing in with username and password and pasting a cookie are still available as tabs.

Security

• Lock the manager with your master password: with Ctrl+L, after a period without input, or
  when the window is minimized. Wrong passwords slow down further attempts.
• Copied secrets clear themselves. Cookies, API tokens and 2FA codes leave the clipboard after
  30 seconds (adjustable) and are kept out of Windows clipboard history and cloud sync.
• The proxy password, web API token and Discord webhook are now stored encrypted.
• Local web API hardening. Requests from web pages and from foreign host names are refused,
  /launch and /close require POST, /cookie is off until you allow it, and repeated wrong tokens
  are throttled.
• Plugins are off by default. If you already have plugin DLLs installed they stay enabled after
  the update.
• Discord webhooks only accept discord.com links, CSV exports can no longer carry spreadsheet
  formulas, and the channel between two running copies of the app only accepts your own Windows user.
• The updater only installs files from GitHub, and a download that fails verification is deleted
  instead of being retried as the same broken file.

Keeping up with Roblox

• FastFlags follow Roblox's allowlist. Since September 2025 Roblox ignores flags that aren't on
  it. Options that stopped working were replaced with ones that still do, and flags Roblox ignores
  are listed instead of silently doing nothing.
• The FPS cap is written to Roblox's own settings file, the same value as the in-game frame
  rate option. The old FastFlag unlock no longer works.
• Friends load through Roblox's current endpoint, which also fixes missing names.
• A failed status request no longer shows every account as offline for a moment.

Fixes

• An account's color tag is saved again.
• Closing a client on purpose no longer triggers auto-rejoin.
• Scheduled tasks that launch a preset work again.
• An account whose saved cookie can't be decrypted keeps its encrypted value instead of being
  overwritten with an empty one.
• Cancelling the private browser download no longer crashes the app.
• Hotkeys are blocked while the manager is locked, and Close all Roblox clients uses the same
  safe path as the button.

Good to know before updating

• Your settings are migrated automatically. The old file is kept as settings.json.v0.bak in the
  data folder.
• The old theme presets become accent colors. Custom colors from 1.x are reset, because the color
  names changed.
• If you used the FPS unlock, its value becomes the new FPS cap.
• Rolling back to 1.7 works (Settings → Updates → Roll back), but 1.7 can't read the encrypted
  proxy password, API token and webhook. Enter them again there.
• Scripts using the web API: send POST for /launch and /close, and turn on Allow reading
  cookies if a tool needs /cookie.

---

Download: RobloxAccountManager.exe (56.4 MB) — one portable file, nothing to install.

RobloxAccountManager.exe SHA-256: b910733e46307666921eb665a961e9d2f079c3f7957821b2ae4a30d9900be619

The in-app updater verifies this checksum before it replaces anything, and keeps your previous version so you can roll back from Settings -> Updates.

v1.7.0

v1.7.0 — 2026-09-09

Updating is no longer a leap of faith

The self-updater downloaded a file and copied it straight over the running application. Nothing
checked that the file was the application, and nothing kept the build being replaced. A download
truncated by a dropped connection, a GitHub error page returned instead of the binary, a captive
portal's login page — each of them "succeeded" as far as the transfer was concerned, and each of
them left an app that would not start and no way back short of reinstalling by hand.

• Downloads are verified before anything is replaced. The file must begin like a Windows
  executable, match the size GitHub reported, and match the SHA-256 published in the release notes.
  Releases are built by a workflow that computes that checksum from the very binary it uploads.
• Your previous version is kept. The build being replaced is moved aside rather than
  overwritten, so Settings → Updates → Restore previous version puts it back. A swap that fails
  halfway now undoes itself instead of leaving nothing behind.
• Interrupted downloads resume. Losing the connection at 95 % of 56 MB used to mean starting
  over; the transfer now continues from where it stopped and retries by itself up to three times.
• The progress window says something useful — transferred, speed and time remaining, rather
  than a bare percentage.
• The right asset is picked. The updater took the first .exe attached to a release, so any
  second executable added later would silently have become what everyone downloads. It now matches
  on the asset name.

You decide when the app looks for updates

There were no update settings at all: the check ran every five minutes, forever, and the only way
to influence it was not to run the app. Settings → Updates is new.

• Check automatically on or off, with your own interval (default: hourly instead of every
  five minutes) and an independent check at startup.
• Skip this version — on the update prompt, on the title-bar pill's right-click menu, or from
  Settings. The release stops being offered; the one after it still is. Turning update checks off
  entirely was previously the only way to stop being asked.
• Include pre-releases, for anyone who wants test builds before they are final.
• The background check now uses conditional requests, so a poll that finds nothing new costs
  nothing against GitHub's 60-requests-per-hour anonymous budget. When the budget is spent anyway
  the app says so and waits, instead of reporting "you're on the latest version" — which it had no
  way of knowing.

Start with Windows

A tray application with no way to start with the system. Settings → Interface → Start with
Windows adds an entry under your own user account — no administrator rights, no service — and
Start minimized opens it straight into the tray. The app is portable, so the entry is re-pointed
at the executable on every start; moving or renaming it no longer leaves a shortcut to nothing.

Playtime

The app knew exactly when each client started and threw that away when it closed. Sessions are now
recorded per account, so there is an answer to "how much has this account actually played".

• Total and last-7-days playtime on the account card, in the account details, and on the
  Dashboard, plus when each account was last played.
• Stored locally in data/playtime.json; six months are kept, sessions under 20 seconds are
  ignored, and clients still running when you close the app are counted rather than lost.
• Off with one switch in Settings → Live data, and the history can be cleared there.

Releases are built by GitHub

Every release was produced on one machine and uploaded by hand — which is also why a checksum was
never published. Pushing a tag now builds the exe on GitHub, fails the build on a single compiler
warning or a tag that disagrees with the project version, takes the release notes from this file,
and attaches the binary together with its SHA256SUMS.txt.

---

Download: RobloxAccountManager.exe (56 MB) — one portable file, nothing to install.

RobloxAccountManager.exe SHA-256: 38a71836b5a9822fd48af8caff358bea603a47617afc3a41745b855e411df4c2

The in-app updater verifies this checksum before it replaces anything, and keeps your previous version so you can roll back from Settings -> Updates.

Roblox Account Manager v1.6.0

Sign in with a username and password

Adding an account used to mean pasting a .ROBLOSECURITY cookie, which means opening browser
developer tools and knowing which value to copy. That single step is where most people got stuck.

Add account now opens on a Sign in tab: type the Roblox username and password, and the
session cookie is fetched automatically and validated before the account is stored.

• Two-step verification is handled in the dialog. When the account has 2FA on, a code field
  appears and says where the code comes from — the authenticator app or the email Roblox just sent.
• Captchas fall back to a real browser. Roblox answers some sign-ins with an Arkose puzzle or a
  device confirmation, which nothing but a browser can display. Sign in in a browser window
  instead opens the genuine Roblox login page in a throw-away profile, waits for you to finish, and
  picks the session up over the DevTools protocol. The profile is wiped the moment the window closes.
• Pasting a cookie still works — it moved to the second tab and is unchanged.

The password is posted to Roblox's own login endpoint and to nothing else. It is never written to
disk, never logged, and never kept once the dialog closes; only the cookie Roblox hands back is
stored, encrypted exactly like every other account.

Changelog handling

The repository carried one release_notes_vX.Y.Z.md per release, and the build embedded whichever
file matched the version. Four releases in, that was four files, and a version bump silently shipped
with no changelog at all if the matching file was missing.

There is now a single CHANGELOG.md. The whole file is embedded and the app slices out the section
for the version it is running, so releasing means adding a section and bumping the version — nothing
else. What's new gained a Full changelog toggle that shows every past version from the same
embedded copy, offline.

Fixes

• Cookie validation marked healthy accounts as dead. The startup check treated any failed
  lookup as a rejected cookie, so an HTTP 429 — which validating several accounts at once provokes
  by itself — or simply being offline flagged good accounts invalid and sent people off to re-add
  them. Only an explicit 401/403 from Roblox counts now; anything inconclusive leaves the previous
  state alone.
• The browser download prompt could open behind the dialog that asked for it, which was
  indistinguishable from the app freezing, since a modal window blocks input everywhere else.

Full Changelog: v1.5.1...v1.6.0

Roblox Account Manager v1.5.1

What's new in v1.5.1

Coming from v1.4.0? This release contains the whole v1.5 line — v1.5.0 was tagged but never
published, so everything below is new to you.

Works with Bloxstrap, Froststrap, Fishstrap and friends

The app assumed Roblox always lives in %LOCALAPPDATA%\Roblox\Versions. On a machine where a
third-party bootstrapper owns the install that folder can be absent entirely — the client sits
under the launcher's own directory instead. Three things were wrong as a result:

• the self-check reported "Roblox is not installed" on a perfectly working machine
• FastFlags and the FPS cap were written to a folder no client reads, so they did nothing
• even when written to the right version folder, a bootstrapper regenerates that file on every
  launch from its own copy — so the flags were wiped before the client ever saw them

Install discovery now follows the roblox-player:// protocol handler, which is the authoritative
answer to "what actually starts when we launch", and falls back to every known layout. Flags go to
the launcher's managed settings file where one exists, and are merged rather than
overwritten, so the flags you set in Bloxstrap/Froststrap yourself survive.

Settings → About now shows which client is installed and who handles launches.

Fixes

• "What's new" said "Release notes could not be loaded." The changelog had exactly one source:
  the GitHub release for the running version. That fails when the release isn't published yet, the
  machine is offline, or the unauthenticated GitHub API limit (60 requests/hour per IP) is spent.
  The notes are now compiled into the exe, so the window always has content; GitHub is a fallback.
• No way to check for updates on demand. The background poll runs every 5 minutes but is silent
  when there is nothing new, so "up to date" and "the check is broken" looked identical. Settings →
  About has a Check for updates button that always reports an outcome, a line saying when the
  last check ran and what it found, and a What's new in this version button to reopen the
  changelog at any time.

New

• RAM trimming. Trim now hands every tracked client's idle memory back to Windows, with an
  optional automatic trim on an interval. The status line reports how much was released. Note this
  is not a permanent saving — the pages return when a client touches them again; it helps when
  several clients are open and the machine starts to run short.

---

Everything from v1.5.0 (never published separately)

Several complete features shipped in earlier builds but could never be switched on: their flags
defaulted to off and no page bound to them. Some had never run in any release.

Feature	Where
Anti-AFK — interval, key, restore-focus, run-one-pass-now	Settings → Automation
Crash watchdog + per-account Auto-rejoin	Settings → Automation / account details
RAM monitor — live per-client readout, optional cap	Settings → Automation
FastFlags — 4 presets, raw JSON editor with validation	Settings → FastFlags
Per-account FastFlags, merged over the global set	Account details
Two-factor codes — local TOTP with countdown and copy	Account details
Global hotkeys — click a row, press the chord	Settings → Global hotkeys
Local control API — token generation, port, endpoint list	Settings → Local API
Proxy — address, credentials, connection test	Settings → Proxy
Encrypted backup / restore — portable, merges on restore	Settings → Security
Economy toggle, presence cadence, cookie validation, rotation capture, audit log	Settings

Fixes from v1.5.0

• Unlock FPS never took effect — it wrote ClientAppSettings.json to a path the modern client
  does not read. (v1.5.1 finishes this: it now also reaches bootstrapper-managed installs.)
• The FastFlags engine had no caller at all. It now runs on the launch path.
• Proxy settings were inert — saved and displayed, but the HTTP client was built once with no
  proxy, so every Roblox call went out over the direct connection regardless.
• Presence could not be re-enabled without restarting — the poll loop refuses to start while
  the setting is off, so no timer existed to resume.
• The Friends tab never auto-selected an account — its picker was seeded before the account
  store finished decrypting, so it always landed on nothing.
• The server browser dropped your selected server when the sort mode changed.
• Restored backups came back unusable — the format never stored the user id, which nearly
  everything keys off.
• Refreshing spent one Robux request per dead cookie; invalid accounts are now skipped.
• The debounced Place ID lookup leaked a CancellationTokenSource on every keystroke.

Security

• The backup password minimum is 12 characters, deliberately stricter than the master password.
  accounts.dat keeps every cookie individually DPAPI-wrapped, so cracking its password still
  leaves the cookies bound to the original Windows user. A backup stores them raw by design — that
  is what makes it portable — so its password is the only barrier, and the file is meant to travel.
• API tokens come from a 192-bit cryptographic RNG. The control server stays bound to 127.0.0.1
  and every route except /ping requires the token.
• Test proxy sends no cookie, so pointing it at an untrusted proxy cannot leak a session.

Full Changelog: v1.4.0...v1.5.1

Roblox Account Manager v1.4.0

What's new in v1.4.0

Multi-instance now works for launches started outside the app

This is the headline fix. Roblox enforces single-instance with two guards, and the app only ever defeated one of them:

Guard	Where it lives	Before
ROBLOX_singletonMutex	global named mutex	held open ✅
ROBLOX_singletonEvent	inside each client process	untouched ❌

Because of the second guard, pressing Play on roblox.com, launching from the Roblox home screen, or opening a Discord invite while a client was already running did not open a new window — the new client handed its launch URL to the running one and exited. Launches from the manager itself were unaffected, since those carry a fresh auth ticket the running client accepts, which is why the problem looked inconsistent.

The new guard clears that per-client lock in every running client and keeps doing so via a lightweight watcher, so a client the app never started is treated exactly like one it did.

New

• Multi-instance guard panel (Settings → Launch) — live status, a Fix multi-instance now button, and a Restart as administrator option that appears only when elevation would actually help
• External clients are managed too — clients started from the website or home screen are adopted into the registry, so Anti-AFK, the RAM monitor and the window grid can reach them
• Self-check (Settings → Diagnostics) — verifies the Roblox install, the roblox-player protocol handler (and warns when another launcher has hijacked it), data-folder writability, free disk space, Roblox API reachability, and the multi-instance guard
• Diagnostics log — one rotating, cookie-scrubbed log with an in-app error counter, Open log folder and Clear log
• Client window controls — arrange every client in a grid, minimize all, restore all

Fixes

• Data loss: an account file that failed to decrypt (typically copied from another Windows user or PC) silently loaded as empty, and the next save overwrote the real file and its backup. The app now refuses to start and tells you where the file is.
• Wrong client attribution: two accounts launched close together were deterministically swapped — the wrong cookie on auto-rejoin, and "close previous client" killing the other account's window
• Untracked clients: attribution was a single attempt 4 s after launch; a slow client start meant it was never tracked at all — no Anti-AFK, no crash watchdog, no RAM cap, and nothing said so. Now retried for 24 s.
• PID reuse: tracked PIDs were never re-validated, so a recycled PID could have the RAM monitor kill, Anti-AFK type into, or the scheduler close an unrelated application
• Rate limiting: an HTTP 429 (exactly what launching several accounts in a row provokes) was treated as "this cookie is dead" and marked good accounts invalid. Only 401/403 do that now.
• Anti-AFK no longer sends its keystroke when the client window fails to take focus — it used to type Space/W into whatever you were doing
• Scheduler auto-close now only closes the clients that task started, instead of every client of those accounts
• Mutex thread affinity: the multi-instance mutex was acquired on whichever thread ran a launch and released from another, which always threw and was silently swallowed. It now lives on its own thread.
• Crash reports append instead of truncating — a repeating fault no longer destroys the evidence of the first one

Under the hood

• New services: RobloxSingletonService, DiagnosticsService, HealthCheckService, InstanceControlService
• Handle-level singleton clearing via the process handle table (NtQueryInformationProcess → DuplicateHandle with DUPLICATE_CLOSE_SOURCE), with a system-wide fallback for older Windows
• Failures the user can act on now surface as a toast or a status line instead of an empty catch
• Clean build: 0 warnings, 0 errors

Note

Roblox's anti-tamper can refuse the process handle on some systems. If that happens the app says so explicitly and offers to restart with administrator rights — it no longer just quietly does nothing.

Full Changelog: v1.3.3...v1.4.0

Roblox Account Manager v1.3.3

What's new in v1.3.3

New

• Smoother UI everywhere: animated page transitions plus soft hover/press fades on cards, buttons and list items
• Buttons polished: subtle scale/opacity feedback and animated icons (hover wiggle, press shrink)
• Presence detection is much faster: shorter poll cadence and an instant refresh right after account actions

Fixes

• Card glow toned down: smaller reach, no more bleeding deep into card content
• "Update available" state now shows reliably after background update checks

Under the hood

• Dropped the entire WinForms framework from the bundle — tray icon and global hotkeys now run on native Win32 (Shell_NotifyIcon / RegisterHotKey via HwndSource)
• Single-file exe shrunk from 63.2 MB to 55.9 MB with zero feature loss
• Clean build: 0 warnings, 0 errors

Full Changelog: v1.3.2...v1.3.3

Roblox Account Manager v1.3.2

What's new in v1.3.2

New

• Card glow reworked: the glow now tracks edge proximity and fades smoothly with distance, giving cards a subtle liquid-glass look on hover

Fixes

• "What's new" dialog no longer shows twice (before and after an update download)
• App-browser sessions are now ephemeral: cookies and profile data are wiped after every browser use, with retries for locked files

Under the hood

• All Roblox API HTTP responses are now properly disposed (fixes slow socket/handle buildup over long sessions)
• Web API responses are fully released after each request
• Background tasks (presence polling, cookie validation, CLI forwarding) now log unexpected setup errors to error.log instead of failing silently
• Clean build: 0 warnings, 0 errors

Full Changelog: v1.3.1...v1.3.2

Roblox Account Manager v1.3.1

What's new in v1.3.1

Fixes

• Fixed a nullable-reference warning in the update prompt flow (CS8602)
• Clean build: 0 warnings, 0 errors

Website

• The project website now deploys from the dedicated gh-pages branch — the main repo stays clean
• Refreshed, more modern layout with subtle animations

Full Changelog: v1.3.0...v1.3.1

Roblox Account Manager v1.3.0

What's new in v1.3.0

Update experience

• Rich update prompt — when an update is available you now see the current vs. new version, publish date, download size, the full changelog and a direct link to the GitHub release.
• "What's new" window — after an update installs, the app shows the changelog for the version you just received (once, on first launch).
• Update metadata (version, date, size, release notes) is pulled live from GitHub Releases.

Under the hood

• New shared release-notes renderer for update windows.
• Version bump 1.2.7 → 1.3.0.

Full changelog: v1.2.7...v1.3.0