League of Legends Nuzlocke Challenge

A League of Legends Nuzlocke borrows the permanent-consequence idea from classic challenge runs and applies it to the champion roster. The common rule is simple: once you lose with a champion, you cannot use that champion again during the run.

OneLifeHero calls this format One Life Hero. It preserves the recognizable Nuzlocke rule while adding queue eligibility, streak states, match evidence, rank movement, and an explicit record of games that should not affect the campaign.

A One Life Hero run can use Ranked Solo/Duo, Ranked Flex, or Normal Summoner’s Rift games. The run owner selects the eligible environment before playing so a casual warm-up cannot silently change a ranked campaign.

Arena uses a different success condition and belongs in the Arena champion challenge format. Separating queue rules prevents augments, placements, and Arena items from leaking into Summoner’s Rift statistics.

OneLifeHero does not ask players to review every match manually. Sync evaluates the match against the run state. If a player queues a champion who is already Fallen, the match is automatically flagged, kept in the audit trail, and excluded from LP progress and performance statistics.

Excluded games remain visible because an honest challenge record should explain what happened. The interface shows the reason, the state before the match, and the totals after exclusion rather than deleting inconvenient evidence.

A useful tracker answers more than who won. It should show which champions remain available, who has earned a streak, why a match counted, which loss caused an elimination, and what valid action comes next.

OneLifeHero also keeps lightweight items, runes, lane context, death locations, and champion-role patterns where Riot match data supports them. These details help explain the campaign without turning the page into a generic match-history clone.