A standalone Roblox account and marketplace tool. Every byte of networking happens in a native Rust core that pools HTTP/2 connections, retunes itself to the rate limits Roblox reports, and decodes JSON with SIMD. The WinUI 3 shell drives it over a C ABI and never touches the network itself.
.ROBLOSECURITY. Full purchasing surface, no captcha, survives restarts. Recommended.auth.roblox.com/v2/login, handles the two step challenge, and finishes through the v3 two step login endpoint. When Roblox raises a FunCaptcha the tool surfaces the challenge id and Arkose key rather than pretending it worked.Accounts live in an AES-256-GCM vault keyed with Argon2id.
hyper client over rustls with ALPN negotiated HTTP/2, adaptive flow control windows and keep-alive pings. Connections are reused across every Roblox host, so there are no repeated TLS handshakes.x-ratelimit-limit and x-ratelimit-remaining off every response and retunes each per-host token bucket to the quota actually granted. On a throttled datacenter IP this took a benchmark from 2 of 40 requests succeeding to 40 of 40.simd-json with a serde_json fallback, measured at 689 MB/s and 25 microseconds per 60 item catalog page.From a datacenter IP with no session, measured directly:
catalog.roblox.com/v1/search/items - 1 request per 60 secondsgroups.roblox.com/v2/groups - 1 request per second, 100 group ids per callusers.roblox.com/v1/users/{id} - 30 requests per 60 secondsA signed in session from a residential address opens these up substantially. The limiter adapts either way, but the sweep is close to useless anonymously and works properly on a real account.
crates/rblx-core - the engine: HTTP, auth, API surface, ops, encrypted vaultcrates/rblx-cli - rblxtool, the full featured command line clientcrates/rblx-ffi - rblx_core.dll / librblx_core.so, the C ABIui/RblxTool - the WinUI 3 desktop applicationThe CLI and the desktop app are the same engine; the CLI is what gets tested against the live API.
Browse the whole tree in the reader below, or take the archive above.