Live Game TUI¶

Follow an active League of Legends game in your terminal. The dashboard combines spectator data with champion metadata and ranked records, and keeps checking when the player is between games.

Installation¶

Install the optional tui extra in your Python environment:

pip install "riotskillissue[tui]"

This includes the Textual interface; Rich and the CLI are included in the base package. See getting started for Python requirements.

API Key¶

Create a key in the Riot Developer Portal and set it in your current terminal:

export RIOT_API_KEY="RGAPI-your-key-here"

$env:RIOT_API_KEY = "RGAPI-your-key-here"

set RIOT_API_KEY=RGAPI-your-key-here

Quick Start¶

Use the player's exact Riot ID and their platform route:

riotskillissue-cli live "GameName#TagLine" --route euw1

Press r to refresh, or q / Esc to quit. The default refresh interval is 30 seconds.

What You See¶

When a Game is Active¶

When Not in a Game¶

The waiting screen continues checking for an active game on the same refresh schedule. A missing Riot account is an error; only a missing active spectator game enters this state.

Usage¶

Basic¶

riotskillissue-cli live "GameName#TagLine" --route euw1

With Options¶

Use a different platform or refresh interval:

riotskillissue-cli live "GameName#TagLine" --route kr --refresh 15

All Options¶

Regions¶

Use a platform route for the player's server: for example, euw1 for Europe West, na1 for North America, or kr for Korea. A regional cluster such as europe is not a platform route. See routing for route families and inference.

Keyboard Shortcuts¶

Features¶

Refreshes run in the background, so the interface remains responsive during slow requests. Repeated refresh keypresses share the active fetch; the countdown starts again after that fetch finishes.

The dashboard keeps a Riot client open until you quit, preserving pooled connections, learned rate limits, and cached Data Dragon content. Quitting cancels any active fetch and closes the client.

Rank Colors¶

Ranks use tier colors. Ranked win rates of 55% or higher appear green; those of 45% or lower appear red.

Programmatic Usage¶

import os

from riotskillissue.tui import run_tui

run_tui(
    api_key=os.environ["RIOT_API_KEY"],
    game_name="GameName",
    tag_line="TagLine",
    region="euw1",
    auto_refresh=30,
)

import os

from riotskillissue.tui import LiveGameApp

app = LiveGameApp(
    api_key=os.environ["RIOT_API_KEY"],
    game_name="GameName",
    tag_line="TagLine",
    region="euw1",
    auto_refresh=30,
)
app.run()

For repeated programmatic fetches, fetch_live_game_data accepts an optional client= argument. The caller owns that client's credentials and lifecycle; region still selects the lookup route. Without client=, each call creates and closes its own client.

Troubleshooting¶

"Not currently in a game"¶

The player needs an active game reported by Riot's spectator API. Champion select does not count. Leave the dashboard open to keep checking, or press r after the game starts.

"404 - Data not found"¶

Verify the exact Riot ID and tag line, then check --route against the player's server. A missing account produces an error instead of entering the waiting screen. If the key is rejected, check or renew it in the Developer Portal.

Partial or previous data¶

Anonymous players and bots do not trigger ranked requests. A successful refresh clears the stale-data notice.

Rate Limiting¶

Each refresh can make multiple requests for account resolution, spectator data, and eligible players' ranks. Retries and other applications using the same key also affect request usage. Increase --refresh above the 30-second default to reduce API usage.