Riot Skin Disabler (NoSkin)
by Moga · 19.4k installs
by Moga · 19.4k installs
by sirdy789 · 4.0k installs
by lawarmor · 3.6k installs
by 1gem1 · 2.9k installs
by FrogCs · 2.8k installs
by Cam · 1.9k installs
by 1gem1 · 1.8k installs
by Aropatnik · 1.6k installs
by YoutZo · 1.5k installs
by p1mek · 1.4k installs
by Aropatnik · 1.1k installs
by Aropatnik · 929 installs
by northoff · 719 installs
by Aropatnik · 704 installs
by Sofi9 · 203 installs
Chud finds the running League client by itself and connects over the local League client API — nothing to configure.
Search for Kassadin and click install on any skin. No accounts, no manual files.
Your install shows up automatically on Kassadin’s “Your mods” row in champ select.
Lock in Kassadin, 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.