Lock in.
Runes land 0.25 s later.

LANEGAP reads champ select from the League client and sets runes, spells and items itself.

Rune page 0.24 to 0.25 s after the lock, spells and item set within 0.04 s. Live client, game version 16.22 (patch 26.22), 1 session: Practice Tool and 1 normal draft, 2026-11-10.

  1. 0.00 s Lock Locked
  2. 0.04 s Summoner spells Set
  3. 0.04 s Item set Set
  4. 0.25 s Rune page Set
Loadout: engine output for the first draft below. Times: the upper bounds of the live measurement.
0inputs per draft
Nothing to type, import or click. 6 simulated drafts, 18 runs.
5picks before the lock
Up to 3 best and 2 carries for the player's role, each with its reason.
3plan lines per lane
Each cites its facts by id. Cooldowns and ranges come from the patch's game data; a line whose number is not in its facts is rewritten.

Sample drafts

Four drafts, read by the engine.

Real output of the rules engine on game version 16.22, with the model off. Pick a draft, then a moment.

This explorer needs scripts. The sections below describe the same behaviour in words.

Engine output, in this site's own layout. The app's window shows these reads, picks, loadout and plan in a narrower page. A pick tagged Profile gets a bonus from the player's own playstyle profile; a champion without one is built from rules.

How it runs

One draft, four moments.

  1. An enemy locks

    Each locked enemy gets its top 2 roles as percentages. Hovers get no read.

  2. Before the lock

    3 best picks and 2 carry picks, each with a score and a reason. Nothing picks for the player.

  3. The lock

    A legal loadout from the rules is in the client before any model call: 1 rune page, spells with Flash on the player's key, 1 item set.

  4. Game start

    The page freezes. No timers, no prompts, no advice from live game data.

Compared

Measured against 1 public web draft tool.

6 bot-lane drafts each, 2026-11-10. The other tool is a web page; its desktop app was not tested. LANEGAP ran on a simulated client unless a row says live.

Measure LANEGAP Web draft tool
Inputs per draft 0 13 to 22: 22 with the lane partner and 5 enemies entered (16 clicks, 6 typed names)
Enemy roles Inferred as percentages: a Bayesian posterior over role assignments Each chosen by hand
Runes, spells, items in the client Set in 6 of 6 drafts. Live: rune page 0.24 to 0.25 s after the lock None. It shows no runes, spells or items and writes nothing
Reasons Pick reasons, built after this measurement: 18 of the 20 picks in the drafts above name an ability. Plan numbers are checked against the facts each line cites. Scores only: 0 of 176 recommendation tiles cite an ability
Pick list 3 best and 2 carries before the lock. Built after this measurement; not timed. Yes, in about 1.2 s, scoped by rank and region, in 7 languages
Runs as 1 local Windows window beside the client. No Overwolf, no overlay, no ads A web page, no install

Speed is not compared: the web tool needs typed input, LANEGAP needs none.

Limits

What it never does.

These limits come from Riot's policy and the product's own rules. No setting lifts them.

  • Never plays for the player

    No pick, ban, lock, accept, dodge or chat message.

  • Never touches a personal rune page

    It writes 1 managed page, tracked by its ID, or a temporary page when every page slot is full.

  • Never reads game memory

    It reads champ select from the client's local API. From the game it asks Riot's own game API one thing: has the game started. No memory access, no injection.

  • Never advises from live game data

    The page freezes at game start. The item set stays in the shop as written in champ select; its first block title carries 1 plan line.

  • Never shows a player's identity

    No names, ranks or stats. Streamer Mode players are never identified.

  • Never estimates MMR

    And never helps anyone dodge.

  • Never shows ads

    Not in the app, not on this site.

  • Never overrides the player's edit

    Edit runes or spells in the client and they stay as edited for that champ select.

Riot's rules

Built around Riot's third-party policy. Registration with Riot precedes the app's public release. The client's local API is unsupported by Riot and can change in any patch.

Availability

Private Windows build, in testing by 1 player. No public download yet.