CUSTOMER RELEASES

What’s new.

The customer-facing changes behind the current native Windows build, from clearer queue behavior to licensing, overlays, service awareness, and safer updates.

V2.2.18 · CURRENT

Forward-only updates and durable activation

The official update path now keeps the installed app current without making customers re-enter their key or exposing a downgrade path.

The updater rejects malformed, equal-version, and older packages before changing the installation.
The Setup installer also refuses to replace a newer installed build with an older one.
Your saved key remains protected in Windows Credential Manager during updates and automatic repair.
Retired builds cannot activate or renew access after the service minimum advances.
A failed forward install can recover privately, but the recovered build still has to pass the current license and version policy.

V2.2.13

Smart safety rests

Optional sender-specific rests now use an open zone, gradual rest chance, short stretch pauses, and a hard endpoint instead of one rigid “12 invites, 3 minutes” rule.

V2.2.11

Courtesy pacing profiles

Choose Steady, Natural, or Relaxed pacing. The dashboard shows the active profile and real next-action countdown while VRChat’s Retry-After guidance always takes priority.

V2.2.9

Official service awareness

VRChat’s official API status now appears while signed in or out. Confirmed API incidents hold pending work and resume only after service recovery.

V2.2.8

Easier activity review

Dashboard and Activity feeds gained persistent scrollbars, mouse-wheel and keyboard navigation, preserved reading position, and corrected Friend/trust-rank colors.

V2.2.4

Simplified Automation Status

The dashboard now prioritizes queued work, queue split, sent/skipped/failed results, sender health, online friends, and the next action—without internal diagnostic noise.

V2.2.3

Predictable queue behavior

Group candidates stay in FIFO order, newly-online friends keep priority over the initial snapshot, permanent recipient outcomes are removed once, and secondary routing stays strict.

Update integrity: the public feed contains version metadata, compiled Windows packages, and SHA-256 checksums only. The in-app updater checks repository origin, expected size, and checksum before restart and accepts only a newer target version. A temporary startup-recovery copy is private repair—not a selectable downgrade—and recovered builds remain subject to the current license and minimum-version policy.

Explore the product