Pengu Loader is an MIT-licensed, C++-built plugin loader that injects JavaScript plugins directly into the League of Legends Client, giving plugin authors and client customizers a way to restyle and extend that client with modern web tooling.

What it is

Pengu Loader — formerly known as League Loader — is a plugin loader tailored for the League of Legends Client. It is written in C++ and released under the MIT licence, and its purpose is to load JavaScript plugins directly into the client so that the interface can be transformed, new features added, and custom content integrated. The repository's topics map the ground it covers: the League Client, the LCU and the LCU API, DevTools, JavaScript, TypeScript, and the project's own pengu-loader and league-loader names. The metadata shows a maintained project rather than an abandoned one, with a last push dated 10 August 2026, 753 stars, 85 forks and 5 open issues.

The concrete problem it solves is extension. The League of Legends Client does not offer third-party developers a documented path for changing how it looks or behaves, and Pengu Loader supplies that missing layer: plugins written in modern JavaScript are loaded into the running client, and personalisation is built on flexible web stacks rather than on patching the client directly. The project also carries its own history in its naming — the same loader was previously distributed as League Loader, and both the pengu-loader and league-loader topics remain attached to the repository, so documentation and community discussion for either name point at the same codebase.

Key capabilities

• Loads JavaScript plugins directly into the League of Legends Client, which is the core function the whole project is organised around.
• Provides plugin support for customising the League Client, so behaviour and content can be extended rather than merely restyled.
• Enables personalisation and theming through flexible web stacks, meaning the client's presentation is shaped with web technologies.
• Offers modern JavaScript compatibility, so plugins can be written against current language features rather than an older embedded runtime.
• Ships built-in DevTools, which makes plugin debugging part of the loader instead of a separate setup step.
• Exposes simplified API access and hooks, with the repository topics pointing specifically at the LCU and the LCU API.
• Distributes signed Windows builds: free code signing on Windows is provided by SignPath.io, with the certificate supplied by SignPath Foundation.

Who uses it and how

• Plugin developers write JavaScript plugins against the loader's API and hooks, then debug them in the built-in DevTools without leaving the client.
• Theme and skin authors use the flexible web stacks to restyle the interface, treating the client as a web surface rather than a fixed UI.
• End users run it on Windows, where the SignPath-provided code signing applies to the distributed builds.
• Developers already working against the LCU and the LCU API can pair their existing client integration work with the loader's hooks.
• The project's scale — roughly 750 stars and 85 forks — describes a community-sized codebase with a small open-issue count, which suits contributors who want a focused surface to work on.

Getting started

The repository does not document an install command of its own; the README directs readers to the project homepage at https://pengu.lol/ to begin. The homepage is the stated entry point for installation and setup.

How it compares

Pengu Loader stands alone in this registry: the supplied facts name no comparable loader and no paid products that it replaces. The only related name in the metadata is its own former title, League Loader, which survives in the repository topics and in the README's naming history.

When to use it — and when not to

Choose it if you want to extend or theme the League of Legends Client in JavaScript and are comfortable that the program is provided "as is", without warranty of any kind, including no guarantee that operation will be uninterrupted or error free. The README is deliberately sparse — installation and usage guidance live on the homepage rather than in the repository — so anyone who needs in-repo documentation, or an officially supported route, should not pick it: the project explicitly states that it is not endorsed by Riot Games, and its disclaimer disclaims responsibility for harm caused by malicious use of the software.

</a>