One update, applied all at once
Updating used to happen in pieces: the mod updated, the game came back, and the launcher updated later - sometimes not until the next launch. Windows could appear mid-way through.
Now it is a single sequence, and nothing opens until every part is done:
- The game closes.
Client.dlland the rest of the mod are replaced.- The launcher is updated silently, and the updater waits for it to finish.
- Only then does one window come back.
You close the game, wait, and everything returns current.
Fix: the launcher said the game was not running
Some players had the launcher report "Ready to launch" while the game was clearly open.
Why: the check asked Windows for the process list, and when that call was refused - some security software blocks it, and it also fails when the game runs elevated and the launcher does not - the error was silently swallowed and treated as "not running". Nothing was logged, so it was indistinguishable from the game actually being closed.
Fix: the launcher now trusts its own connection to the mod first, since that only exists inside a running game. It also falls back to a second detection method that tolerates individual processes denying access, and logs when everything fails instead of quietly guessing wrong.
The mod updater had the same check with the opposite failure: it assumed "not running" and could have overwritten a Client.dll the game had loaded. It now assumes the game IS running when it cannot tell - refusing to update is recoverable, a corrupted install is not.
From 1.7.21
- Discord kept showing the server you just left - your status now updates the instant you switch.
From 1.7.17 - 1.7.20
- The rVclient launcher (beta), worldwide Global chat, rvclient:// invite links, voice mute actually muting voice, and the Discord rejoin/Join fixes.
Known limitations
- The launcher's Friends tab is placeholder data for now.
- Friends seeing "Launch Game" instead of "Join"? That is Discord > User Settings > Activity Privacy, not the mod.