Riot Skin Disabler (NoSkin)
by Moga · 19.4k installs
by Moga · 19.4k installs
by Nyht · 9.6k installs
by FingaMiro · 7.8k installs
by LordksOP · 5.8k installs
by LordksOP · 4.8k installs
by Aropatnik · 3.0k installs
by LordksOP · 2.5k installs
by PoonNotaniShisui · 2.1k installs
by Azure · 1.8k installs
by davex · 1.2k installs
by Aropatnik · 1.1k installs
by Aropatnik · 929 installs
by Cam · 789 installs
by p1mek · 772 installs
by aluna · 375 installs
by Fresh_Fish · 302 installs
Chud finds the running League client by itself and connects over the local League client API — nothing to configure.
Search for Nami and click install on any skin. No accounts, no manual files.
Your install shows up automatically on Nami’s “Your mods” row in champ select.
Lock in Nami, 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.