Built and tested so far
Updated 27 September 2026. Working on now: in-game runtime.
Foundation
In progress · 90%The protocol between Chud and the runtime, the build tooling, and a test gate every change has to pass.
Verified installs and updates
In progress · 70%Installs that cannot be left half-written, signed update checks and rollback protection. Tested; release keys come later.
Code signing
Waiting · 40%Signing account and tooling are set up. Waiting on identity verification before the first signed build.
In-game runtime
In progress · 5%The part that applies skins inside a live game. Lab work only so far, and the bulk of what is left.
Parity testing
Up next17 cases the runtime has to match against the patcher Chud uses today. 0 of 17 passed.
Release and Chud update
Up nextA standalone release first, then it ships inside Chud through the normal updater.
The runtime is the part that gets a skin into the game.
A custom skin tool has two halves. The manager is what you see: it lets you pick a skin and builds the modded files. The runtime is what you don't see: it starts with the game and makes League read those files. Chud already has its own manager. Its runtime is borrowed.
Today that runtime is League Toolkit's patcher, the same pair LTK Manager uses. Chud cannot bundle it, so it downloads the pair on first run and checks for a new one every day. It works, and it stays in place until ChudRuntime has matched it case for case.
Three things we cannot fix from the outside
- Patch weeks. When a League update breaks the patcher, Chud waits on a fix it does not control. With our own runtime the fix ships in a Chud update.
- First run. Skins currently need a second download from another project before they work. ChudRuntime arrives with the app.
- Support. When a skin fails to apply, we can read our own logs and change our own code.
What it does not change: custom skins are against Riot's terms of service, and no runtime is ban-proof. That will be as true of ChudRuntime as it is of every tool today, and the FAQ says so plainly.
Weighted by the work, counted only when tested
Each stage above carries a share of the total based on how much work it is, and a stage only earns progress for what has been built and passed its tests. That is why the in-game runtime, the largest stage, still shows almost empty while the groundwork around it is nearly done. No date is promised. When the bar moves, the build log below says why.
Install store and signed update verification passed the test gate. Signing account set up; identity verification is pending.
Project started. Source audit finished, runtime contract and inspection tools in place.
Get told when it moves
This page is updated every time a stage changes, and it remembers the number you last saw, so you can tell at a glance what is new. Release news goes out on Discord and Reddit first. When ChudRuntime ships it arrives as a normal Chud update, with nothing extra to install.
Can I download ChudRuntime?
Not yet. There is no public build. It will ship inside Chud once it has passed parity testing.
Is ChudRuntime a replacement for LTK Manager?
No. LTK Manager is a full mod manager. ChudRuntime is only the runtime, the piece that applies skins in game, and it is being built for Chud.
Do skins work in Chud right now?
Yes. Chud applies skins today through League Toolkit's patcher, which it downloads for you. ChudRuntime will replace that piece later without changing how you pick skins.
Will ChudRuntime make custom skins safe to use?
No. Custom skins break Riot's terms of service and nothing is ban-proof. A different runtime does not change that.
When will it be finished?
There is no date. The bar at the top of this page is the honest answer, and it was last updated on 27 September 2026.