¶ Overview
Adding child VFX to main VFX systems to create variations and elaborate particles.
If you encounter any issues with this tutorial or you don’t understand part of it, you can ask for help on the Runeforge-Discord server
¶ Required Tools
- Ritobin Tools to translate bin files into Python files
- Choose any Code Editor Visual Studio recommended
If you choose Visual Studio Code, you need the Python extension aswell!
Other editors work aswell, aslong as they can edit .py (Python) files.
¶ Written Guide
We will be focusing on how to add Pool Party Braum’s castles from his Pool Party skin to his base skin. The reason is because BASE Braum utilizes the same mesh with different scales, while Pool Party actually has randomized objects that it pulls from.
The vfx in Pool Party has a probability selection between two children systems.
We will have to add these to one of BASE Braum’s bins, link in resources, and add the linking emitter.
BASE – Refers to any bins related to the base skin. In our case:
braum_skins_skin0_skins_skin3.bin
skin0.bin from the DATA folder
SKIN – Refers to any bins related to the base skin. In our case: braum_skins_skin33_skins_skin34_skins_skin35_skins_skin36_skins_skin37_skins_skin38_skins_skin39_skins_skin40_skins_skin41.bin
Skin33.bin from the DATA folder
Following steps which we’ll go over in detail throughout the post:
- Grab related bins. Regular and DATA for BASE and SKIN you want to pull from.
- Find child systems (R_mis from SKIN and paste as new ones to your BASE bin.
- Copy hashes for each child system’s name and find in the DATA resources of SKIN
- Paste hashes from resources to BASE resources
- Find linking emitter from primary VFX system of that ability in SKIN and paste to BASE version’s.
I recommend pasting to the same bin as your targeted VFX (Our case – R_Mis).
Yes, you can paste the child systems to virtually any bin of Braum’s that you wish, however this makes it easier to stay organized.
In this case, we are grabbing TWO children systems, not just one (since our probability is mixed between two).
Make sure to copy from the bracket below Particle Path
ALL the way up to the VfxSystemDefinitionData
And paste below the last bracket of your targeted VFX system (It's recommended to place it there for organization).
Our BASE bin should look like this now once we have added the new VFX systems and search for particleName: string
Now that we have the new systems added, we immediately have to link them in our resources for skin0.bin from DATA.
Copy the hash name before VfxSystemDefinitionData of one child system and search for it in resources of skin33.bin from DATA.
Now copy and paste that to skin0.bin’s resources.
Here I have both of my child systems highlighted.
Now that I have copied both child system hashes over, I will need to find the linking emitter for both. I can find this in Braum’s bin that contains the VFX system for his R_Mis on his Pool Party skin.
You can search for VfxChildIdentifier to find it easier.
Make sure the hashes are the same as the ones you linked in resources.
Note that this emitter does not have any textures linked (may not always be the case but is most likely). It basically acts as a linking emitter that tells the VFX to pull from another system.
Now that this has been copied to my BASE‘s R_Mis vfx system, I can now test the mod.
For clarity’s sake, I have removed Braum’s original Ice Spikes that appear in the middle of his ult so that we can see the new children.
¶ Sources
- Bearded Shepherd