Frieren Lux
by rorotea · 40.6k installs
by rorotea · 40.6k installs
by Moga · 19.4k installs
by LordksOP · 14.5k installs
by LordksOP · 12.3k installs
by Sinister · 8.5k installs
by FingaMiro · 7.7k installs
by LordksOP · 7.6k installs
by Raka · 6.5k installs
by FingaMiro · 5.9k installs
by LordksOP · 5.0k installs
by LordksOP · 5.0k installs
by LordksOP · 4.0k installs
by LordksOP · 4.0k installs
by LordksOP · 3.9k installs
by rorotea · 3.8k installs
by LordksOP · 2.7k installs
by davex · 2.4k installs
by soul · 2.1k installs
by p1mek · 1.5k installs
by YoutZo · 1.4k installs
by Aropatnik · 1.1k installs
by Aropatnik · 929 installs
by Aropatnik · 588 installs
by YoutZo · 566 installs
Chud finds the running League client by itself and connects over the local League client API — nothing to configure.
Search for Lux and click install on any skin. No accounts, no manual files.
Your install shows up automatically on Lux’s “Your mods” row in champ select.
Lock in Lux, open the Skins grid, and pick the mod you installed.
Custom skins are against Riot's ToS. Chud has no ranked-mode lockout and runs heuristic ModScan checks before Library installation, but that isn't the same as ban-proof — nothing is. Full honest answer in the FAQ.
Often, yes — every League patch can change the game files mods target, so skins commonly break until the patcher and the mod itself catch up. Chud re-checks League Toolkit's patcher daily; if you are coming from CSLOL Manager, the error-by-error guide covers the rest.
Yes. Library mods are standard .fantome packages, the same format CSLOL Manager and LTK Manager install, and Chud applies them with League Toolkit's patcher. File locations and formats are in the docs, and the tools are compared in CSLOL Manager alternatives.