VALORANT Remake, Surrender and AFK Rules: What the Client Actually Tells You

Remake, surrender and AFK penalties often get bundled into one rule in old VALORANT posts. They are separate systems. A remake is a client-offered response to an early disconnect. A surrender is a vote to end a live match. AFK and queue-dodge penalties are actions against the player who leaves or stops participating.

Here is the short version: use a Remake prompt when the client gives you one. If it does not appear, do not assume /ff will create a remake. Riot documents surrender timing and vote thresholds, but it does not currently publish one universal remake recipe.

Start with the Remake prompt

The awkward part is the documentation. I checked Riot Support's current VALORANT pages and recent PlayVALORANT updates, but I could not verify a live Riot page that states one universal remake trigger, timing window and vote threshold for every queue. Riot's Ask VALORANT post from February 2021 discussed possible changes to the remake window and clearer separation between remake and surrender. That is useful history, not a current rule sheet.

So, if the client shows a Remake option, read the on-screen instructions and vote there. If it does not, do not type a command from an old guide or treat a normal surrender as a remake. The prompt in your match is the only place that can tell you whether Riot has offered that option for the queue and situation in front of you.

There is one clear warning for the player who disconnected. Patch 8.11 says AFKs who result in a remade match immediately encounter an intervention, with stronger intervention for repeated occurrences. A remake can save the connected players from playing out a hopeless 4v5, but it is not a free pass for the player who caused the disconnect.

Surrender has a published rule set

Riot's current Surrenders in VALORANT support page says you can call a vote with /surrender, /concede or /ff in chat, or with the in-game Surrender button. The vote becomes available past the start of the fourth round in both the attack and defence phases. If the vote passes, the next round is forfeited. A vote on Round 8, for example, ends the match when Round 9 would start.

The threshold depends on the mode Riot names. Unrated requires 80% of the team to vote yes. Competitive requires a unanimous vote. You get one surrender attempt per phase. If a teammate has already called one before you, your request does not use up your attempt. If a player does not choose a side, the system counts that as a no vote.

Those are the rules Riot publishes for Unrated and Competitive. Do not quietly copy the same threshold into Swiftplay, Premier or a limited-time queue when the support page does not say that it applies. If the match has an early disconnect but no Remake prompt, /ff remains a normal surrender request, with the normal round and mode limits.

AFK and queue dodging cost more than one bad round

Riot's current Penalties and Bans FAQ defines AFK as being away from the computer, behaving as if you are not there, or remaining in the match without participating. Queue dodging means leaving the Agent Select screen by disconnecting from the server, which makes your team start a player down.

The same FAQ lists these possible consequences:

• A warning that the AFK or queue-dodging system was triggered.
• XP denial for the match that caused the penalty.
• A 6–24 RR deduction for AFK or queue dodging in a Competitive match, listed as lasting one match.
• A Teamplay Restriction Timer lasting 3–365 days. During it, only solo Deathmatch and Custom Games are available.
• A VALORANT game ban lasting from 7 days to permanent.

That table is not a promise that every case walks down the list in order. Riot says severity, frequency and behavior history can change the result, and more than one penalty can arrive at once. It also says occasional connection or hardware problems are not meant to be punished severely, but recommends waiting until an unstable connection is fixed before queuing again. A technical excuse may explain a disconnect; it does not make repeated disconnections safe.

Use this decision tree in a live match

1. The client offers Remake. Read the prompt, vote there and do not replace it with /ff.
2. There is no Remake prompt. Keep playing until the regular surrender option is available under the round and mode rules.
3. A surrender vote opens. Check the queue. Unrated needs 80% yes; Competitive needs every participating vote. No response is a no.
4. You are the disconnected player. Return as quickly as you can and keep playing. If the connection is still unstable, stop queueing until it is reliable.

The last distinction matters because XP and RR are not the same system. Riot's surrender page says round-based modes award XP for completed rounds, while Team Deathmatch uses a flat AP and XP rate based on time participated. The Penalties FAQ separately lists the Competitive RR deduction for AFK and queue dodging. Do not use an XP rule to promise a rank result, and do not assume a remake removes the behavior penalty.

If an old guide gives exact remake numbers but cannot link a live Riot page, treat those numbers as historical. In the match itself, trust the prompt you can actually see.

If the notice was about a suspected cheater, use the first-time seeing this message guide. For RR context, see what determines the performance bonus.