Run multiple Roblox clients. Side by side, one machine.
RORORO is a native multi-launcher for Roblox — spawn several clients at once, each signed in as a different saved account, one click each. Native on Windows and macOS, plugin-extensible, free. No injection, no client modification — it holds a singleton lock before launch and starts the official client unmodified.
Get it
Three install paths. Pick the trust posture that fits you — they all land the same app.
Microsoft Store
Signed by Microsoft, bypasses SmartScreen entirely, auto-updates through the Store. One click and you are in — the best path for most people.
Open the Store listingGitHub Releases
Grab rororo-win-Setup.exe — one click, installs to your user profile. SmartScreen warns once because the installer is unsigned; choose More info → Run anyway. Velopack auto-updates it from there.
Homebrew
The Mac-native sibling — signed and notarized by Apple, Sparkle auto-update. Install with one tap:
brew tap estevanhernandez-stack-ed/rororo
brew install --cask rororo
RORORO Mac on GitHub
What it does
The launcher core — the same shape on both platforms, native on each.
One-click multi-instance
A tray toggle holds the Roblox singleton lock so multiple clients run side by side. The official client, unmodified — no injection, no DevTools, no registry edits.
Saved-account vault
Add your alts once via an embedded login window. Cookies are encrypted at rest and tied to your machine — DPAPI on Windows, Keychain on macOS.
Launch As
One click spawns each saved account straight into your default game URL. Set the game once; every alt lands there.
Your password never touches the app
Login happens on Roblox's own page inside an embedded browser. RORORO is the window frame, not the form handler — it only ever captures the session cookie set after a successful login.
State-coloured tray ring
Read your setup at a glance: cyan ring means the lock is held and multi-instance is on, slate means off, magenta means error. No menu-diving.
Auto-update built in
Velopack on Windows, Sparkle on macOS. When Roblox shifts under the launcher, the fix ships to you without a reinstall.
See it work
The surfaces you actually use — the welcome flow, the add-account window, Squad Launch, settings, the diagnostics tab.
Two platforms, one product
Not a port wrapped in a cross-platform runtime — each build is native to its OS, using only public APIs.
RORORO for Windows
- ▸Multi-instance via a singleton-mutex hold — typed P/Invokes, no client touch.
- ▸DPAPI-encrypted account vault — cookies tied to your Windows user; a copied file won't decrypt elsewhere.
- ▸Squad Launch, Friend Follow, join-by-link, per-game routing, local renames.
- ▸The plugin host — v1.4's named-pipe extension surface (see below).
- ▸Velopack auto-update · Microsoft Store + GitHub Releases.
RORORO for Mac
- ▸Multi-instance via POSIX
sem_unlink+ per-launch app copy — public APIs only, no client modification. - ▸Keychain-backed vault — saved cookies never sync to iCloud.
- ▸Embedded WKWebView login — same password-never-touches-the-app contract as Windows.
- ▸A built-in auto-keys macro cycler for AFK keep-alive.
- ▸Sparkle auto-update · signed and notarized by Apple · Homebrew.
Plugins
v1.4 opened RORORO on Windows to plugins — and this is where you find them.
RoRoRo Ur Task
Live · v0.2.0Per-window-aware macro recorder. Records bind to a Roblox account; playback refuses to fire keys or clicks into any other alt's window, and stops cold if you alt-tab away or the bound window closes. F8 to record, F5 to play, Esc to abort. The reference plugin for the SDK.
Session Stats
On the benchLive per-account uptime, launch counts this session, and mutex state — a pure observer panel for tracking a long farming run.
Discord Rich Presence
On the benchPushes "playing with N alts via RORORO" to your Discord status whenever accounts launch.
Auto-Relaunch on Exit
On the benchWatches for an alt's window closing and relaunches it — closes the crashed-alt loop on an unattended run.
- Open Plugins from RORORO's main-window nav, or from the tray menu.
- Paste the plugin's GitHub release directory URL into Install — the parent path that holds its
manifest.json,manifest.sha256, andplugin.zip. - RORORO fetches the manifest and verifies the SHA-256 of the download against it — and refuses to extract on any mismatch.
- Review the consent sheet. Every capability the plugin declared is itemized; toggle each one before it gets access.
- Restart RORORO. Plugins start when RORORO launches, so a fresh install runs after the restart prompt.
A plugin is your own signed Windows app built against the RORORO plugin contract. Ship it as a GitHub release with three artifacts — manifest.json, manifest.sha256, plugin.zip — and anyone can install it with the steps on the left.
The honest part
What this is, what the risk is, and whose work it builds on — said plainly, because it should be.
An independent third-party tool
RORORO is not affiliated with, endorsed by, or sponsored by Roblox Corporation. "Roblox" is a trademark of Roblox Corporation, used here only to describe compatibility — RORORO launches the official Roblox client, unmodified.
No injection — but the risk isn't zero
RORORO doesn't inject into or modify the Roblox client. It holds a Windows mutex name (or a POSIX semaphore on macOS) before launch, then starts the official client. Roblox has stated that multi-instancing "may be considered malicious behavior," so the risk of a ban appears low but is non-zero — and the README says exactly that. Don't run this on accounts you can't afford to lose.
Reuse without erasure
The named-mutex defeat technique originated with MultiBloxy by Zgoly. RORORO is a clean C# reimplementation with substantially expanded scope — account management, structured launch flow, a plugin host — not a fork. The credit, the reference binary, and the caveats are all in PROVENANCE.txt.