riotgames/leaguedirector

Purpose and Runtime

League Director is a Windows desktop tool for directing and recording League of Legends replay footage. It runs on Python 3.10 with PySide6/Qt, connects to the game’s Replay API, and exposes replay, camera, rendering, sequencing, and capture controls. Startup is via run.bat for development; distributable packaging is defined under build/.

Application Bootstrap and UI Shell

leaguedirector/app.py is the likely Qt application/bootstrap boundary, assembling the desktop window and top-level workflows. leaguedirector/widgets.py supplies reusable Qt UI controls, while leaguedirector/settings.py provides persisted application/user settings. This is a native desktop client rather than a web service.

Paths:

• leaguedirector/app.py

• leaguedirector/widgets.py

• leaguedirector/settings.py

Replay API Integration

leaguedirector/api.py is the external-control boundary to a running League replay. The application must detect/connect to the replay API and issue commands for playback, camera, UI visibility, graphics, and capture. The game must have EnableReplayApi=1, and replay availability is an external runtime dependency.

Paths:

• leaguedirector/api.py

• leaguedirector/enable.py

• resources/riotgames.pem

Game Enablement and Installation Configuration

enable.py likely locates League installations and enables/configures Replay API access before a replay begins. This separates local filesystem/game configuration from active API control. Certificate material at resources/riotgames.pem suggests authenticated or TLS-backed communication with game-side endpoints.

Paths:

• leaguedirector/enable.py

• leaguedirector/settings.py

• resources/riotgames.pem

Director Controls and Input Bindings

The central interaction layer maps UI actions and configurable shortcuts into replay API operations: playback speed, FPS camera movement, entity attachment, HUD/UI toggles, and graphical options. Bindings are isolated in bindings.py, allowing user customization without coupling input handling to API transport.

Paths:

• leaguedirector/bindings.py

• leaguedirector/api.py

• leaguedirector/app.py

Sequencer, Keyframes, and Persistence

sequencer.py is the timeline/domain engine for recording and replaying keyframed camera and graphics state. Its control flow is: sample or edit director state → create/edit/blend keyframes → support undo/redo → save/load reusable sequences → apply interpolated state back through the replay API.

Paths:

• leaguedirector/sequencer.py

• leaguedirector/api.py

• leaguedirector/widgets.py

Rendering Assets and Capture

The tool drives replay-side visual settings including skyboxes, fog, depth of field, shadows, clipping, and field of view; bundled DDS skyboxes are local assets selected by the UI and applied through replay controls. Video/image capture produces WebM or PNG output through the game/replay integration rather than an in-repo media server.

Paths:

• resources/skyboxes/ColorBlack.dds

• resources/skyboxes/ColorBlue.dds

• leaguedirector/api.py

Distribution Boundary

Windows distribution is built with scripts/specification under build/, including a PyInstaller-style spec and an Inno Setup installer definition. Development launchers are platform scripts, but documented supported end-user operation is Windows-only.

Paths:

• build/build.spec

• build/install.iss

• run.bat