To remake a League of Legends game, vote Yes when the game automatically offers a remake after an eligible early disconnect or period of inactivity. In current PC Summoner’s Rift, eligibility begins at 0:55 and normally closes at 2:25. Two yes votes end a 4v5; one is enough in a 3v5 or smaller team. You don’t need to wait three minutes or start the vote in chat.
Last verified: September 18, 2026 (UTC) · PC League of Legends · Patch 26.18. This guide focuses on Summoner’s Rift, not VALORANT or Wild Rift.
A successful remake is not a surrender. Active players normally receive neither a win nor a loss and no LP change. The inactive player is penalized, and a ranked premade exception applies to Diamond IV and above. Check that exception before assuming a remake is penalty-free for everyone.
How to remake in League of Legends now
- Keep playing while the game checks the missing or inactive teammate. Don’t go AFK yourself while waiting.
- Watch for the automatic remake vote and the accompanying chat message explaining which player triggered it and why.
- Choose Yes if you want to end the match. The required support depends on how many players remain on your team.
- Stay active until the game actually ends, then check the post-game result before queueing again.
Riot made votes automatic in Patch 26.14. Older instructions telling you that someone must type /remake first describe the previous workflow. The command’s name still appears in Riot’s support documentation, but a chat command isn’t a way around the eligibility rules.
The current remake window and vote requirements
The early-game schedule moved forward in Patch 26.1. A teammate must be identified as disconnected or inactive for at least 55 seconds during the eligible opening period; a brief connection interruption doesn’t automatically qualify.
| Game clock | What happens | What you should do |
|---|---|---|
| Before 0:55 | The game monitors activity, but a remake is not yet available. | Continue normal play and watch for the system message. |
| 0:55–2:25 | An eligible early absence can trigger the automatic vote. | Respond promptly; don’t assume someone else has voted. |
| Near the end of the window | Riot allows at least 30 seconds for a late-eligible remake opportunity. | Follow the displayed vote rather than treating 2:25 as an instant cancellation of an existing opportunity. |
| After the opening window | A newly missing teammate cannot normally open a fresh remake. An already eligible vote may still be concluding. | Do not confuse a later early-surrender offer with a remake. |
For example, an absence that becomes eligible at 2:20 can extend the response opportunity beyond 2:25. That grace period does not mean a player can disconnect for the first time at 2:20 and instantly make the game remakable.
- Four active players against five: at least two yes votes are required.
- Three active players or fewer against five: one yes vote is sufficient.
- One opportunity: Riot permits the remake vote only once. Declining it is not a way to reset the timer.
Does First Blood prevent a remake?
The order matters. Riot says the team cannot remake if its player goes AFK or disconnects after that team gives up First Blood. That is narrower than “any First Blood anywhere cancels a remake.” Don’t intentionally die or leave to try to manipulate the result; the system’s eligibility message is the relevant signal.
Who loses LP or receives an AFK penalty?
Riot’s remake eligibility and penalty FAQ distinguishes the inactive player from everyone who kept playing. A remake does not count toward requirements to complete a number of games, either.
| Player or situation | Result | Important exception |
|---|---|---|
| Active player, not covered by the ranked premade rule | No LP gain or loss; no win or loss on the record. No BE or XP reward. | Keep playing until the match ends so you are not detected as inactive too. |
| Player responsible for the AFK or disconnect | A recorded loss, the normal loss of LP where applicable, and an AFK flag. | A successful vote does not erase the leaver penalty. |
| Diamond IV or higher in the inactive player’s ranked premade | The same remake penalties as the inactive player. | The disconnected friend can be below Diamond; your own rank is what matters for this exception. |
| Normal-game premade | The Diamond ranked-premade exception does not apply. | The actual inactive player can still be punished. |
A Diamond player matched with a random teammate is not penalized just because that random teammate disconnects. Conversely, a Platinum player is not caught by the Diamond exception merely because the friend who disconnected is Diamond. More than one genuinely inactive player can be penalized in the same match.
Riot documents these visible outcomes, not a public calculation of hidden MMR for every edge case. Treat claims that remaking can “repair” MMR or produce a favorable ranked reset as unsupported.
Why isn’t a remake appearing?
- The absence is too recent. Fifty-five seconds of qualifying inactivity is different from fifty-five seconds elapsed since the match began.
- The disconnect happened too late. A later 4v5 does not retroactively satisfy the opening window.
- First Blood happened before the relevant absence. Check the chronology, not just whether someone has a kill.
- The one vote has already happened. A failed vote doesn’t guarantee another attempt.
- The queue has different rules. Don’t apply Summoner’s Rift’s clock to another game or assume every ARAM variant behaves identically. Bot matches are not covered by Riot’s remake system.
If the visible message contradicts what happened, save the match ID, region, game time, and a screenshot of the message for Riot Support. A teammate’s empty lane alone does not establish how the server classified their activity. Keep playing rather than disconnecting to force another vote.
Remake, surrender, and dodging are different
A remake closes a qualifying broken opening without the ordinary result for most active players. Surrender concedes a match that is underway; an early surrender caused by an AFK is still not the same penalty-free outcome. Dodging happens before a match starts and follows its own queue rules. None is a player-controlled rewind to undo a bad trade or an unfavorable champion matchup.
This guide is about ending an eligible match, not shortening every session. For the time commitment of other queues, see our standard ARAM and Mayhem match-length guide. If the vote fails and the game continues, the League beginner guide’s laning and teamfight advice is a better next step than waiting motionless in base.
Quick questions
Do I still need to type /remake?
No. The current system starts a vote automatically when it detects an eligible situation. Typing the old command is not required and cannot make an otherwise ineligible match qualify.
What if the missing player reconnects?
Read the live vote and system message. A reconnect by itself does not tell you how much qualifying inactivity the server recorded. Don’t assume a universal cancellation rule from one match; vote on the offer the game actually presents.
Will a remake finish a required game for me?
No. Riot excludes remakes from completed-game requirements, including low-priority-queue game counts and relevant content-unlock requirements. It is not a shortcut for progression.
Does this also explain ARAM and League Classic?
No. Riot’s general FAQ lists Howling Abyss and rotating modes among supported queues, but this guide’s timing explanation is verified for modern PC Summoner’s Rift. Use the current mode-specific rules and on-screen prompt for other queues rather than transferring every timer from this page.
Optional 1v9 League services
1v9 also lists League of Legends coaching, League of Legends accounts and League of Legends boosting. These commercial services do not change remake eligibility, remove penalties, or override Riot’s rules; they are separate from the instructions above.
What changed in this guide
September 18, 2026: checked the Patch 26.1 timing change, the automatic voting introduced in Patch 26.14, and Riot’s current penalty FAQ against Patch 26.18. Older references to a three-minute start were not carried forward. The current support FAQ still contains some older examples, so its newer timing table and the later patch notes take priority.
-a6d5b3e156bb.webp)
