Riot Skin Disabler (NoSkin)
by Moga · 19.4k installs
by Moga · 19.4k installs
by matth · 11.9k installs
by Maygik · 6.6k installs
by rorotea · 5.4k installs
by Cam · 3.1k installs
by Tet · 2.3k installs
by agomsMoga · 1.9k installs
by 1gem1 · 1.4k installs
by Aropatnik · 1.1k installs
by YoutZo · 949 installs
by Aropatnik · 929 installs
by inaba24 · 868 installs
by rorotea · 756 installs
by YoutZo · 734 installs
by WrongLane · 595 installs
by YoutZo · 303 installs
Chud finds the running League client by itself and connects over the local League client API — nothing to configure.
Search for Aurora and click install on any skin. No accounts, no manual files.
Your install shows up automatically on Aurora’s “Your mods” row in champ select.
Lock in Aurora, 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.