Community · E2 · artifact verified
Play League of Legends with three Jev heads
Jev plays Yasuo in League of Legends through three decision heads - strategy once a second, tactics six to seven times a second while units are on screen, and build checks every twenty seconds - while code reads the game and executes.
01 · Role in the system
What Jev does here
Riot's local Live Client Data API supplies exact stats - health, gold, items, levels, events - and a light color-mask screen read (no model) supplies positions from the minimap, per-unit health bars, and HUD cooldowns. The strategy head answers intent among eight options, a destination choice over nineteen map places, legal level-up abilities, and danger and recall Nouls; the tactics head answers action, target, and distance back to back for the next move; the build head asks which resistances are needed and picks the next item over a shortlist drawn from the full Data Dragon catalog. Code buys the item or its best affordable components and executes every move within one actor tick.
02 · Control boundary
Where Jev sits
Three rate-tiered Jev heads over exact game API plus screen-read state; code owns execution, purchasing, and the actor tick.
Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.
03 · Known limits
What this evidence does not prove
- Uses Riot's local Live Client Data API, so it plays on the player's own machine through sanctioned read-only endpoints; no ranked-integrity testing is claimed.
- Screen reading is color-mask heuristics, so unit detection degrades with unusual skins or overlays.
- Ranks and win rates are not quantified in the README.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- viraatdas ↗Community · github · public · checked 2026-09-25