This tutorial shows you how you can fix your mod if it does not play any champion voices anymore.
This usually happens on new Riot skin releases.
Your skin must have an edited SkinX.bin, if it doesn’t, there must be another issue.
If you encounter any issues with this tutorial or you don’t understand part of it, you can ask for help on the Killerskins-Discord server
or you can contact me directly: Yoru#1006
Table of Contents
Infos
When Riot releases a new skin, a part in skinX.bins usually gets updated and your custom skin does not play any voices anymore.
Only SkinX.bins are affected, so data/characters/champion/skin0, skin1, skin2, skin3, etc. and not .bins directly inside data, like E67150BE212BCA8C.bin.
IMPORTANT: If you want to fix a skin by someone else and your extracted files look like this, it’s best to just wait for the creator to update it.
Required tutorials
In order to follow this tutorial you must understand and be able to follow the following tutorials:
Required tools
- Obsidian
- Ritobin
- Editor for Python files (I recommend Visual Studio Code + Python extension)
Written tutorial
Extracting the new skinX.bin
Extract the matching skinx.bin to your custom skin from Obsidian. Make sure to not extract it in the same location, so you don’t override it and lose your particles.
Then convert it to .py with ritobin by drag-and-dropping the .bin onto ritobin_cli.exe.
Updating the .bin
Open both files side by side in your editor, Visual studio for me.
Now right at the start of the .bins you will find “linked: list[string] = {” and then a long list of .bin files.
When you compare your .bin to the new .bin, you will see that they are different (usually it is even more obvious by the new one simply having more lines):
Mine
New one
Now copy the whole list of .bins from the new .bin file into your edited and outdated one.
Save your .bin.
Converting back the .py and cepacking your mod.
Now just convert the .py back into a .bin by drag-and-dropping the .bin onto ritobin_cli.exe and then repack your mod in CSLoL.
