I've made a script to copy the official BnS content folder to a second one but including mods to keep official installation untouched.
The script creates junctions and hardware links mixing your "Mods" folder with the official BnS contents folder. So, you just have to configure BnS Buddy to point to the new modded BnS folder to do your things, patch xml, keeping the original installation untouched.
The script creates junctions and hardware links mixing your "Mods" folder with the official BnS contents folder. So, you just have to configure BnS Buddy to point to the new modded BnS folder to do your things, patch xml, keeping the original installation untouched.
How it works?
By default, the script is configured to work as below:
- You have pasted the script and the "Mods" folder into the BnS content folder, where there are "bin", "bin64" and "contents" folders.
- You add your mods into "Mods" folder, respecting the folder tree structure of BnS (you will noticed that "bin, "bin64" and "contents" exist into the "Mods" folder, as the original installation folder).
- You start the script and wait for its magic. You will find a new folder, "Modded_Client", which is a mix between your mods and official content.
- Configure BnS Buddy's game custom path to "Modded_Client" instead of official client. You can now patch and do your ritual and human sacrifices as you did before this script exists.
- You want to update a mod? Replace or add you new mod in "Mods" folder, then restart the script. The updating process will be quicker than creating a new "Modded_Client" from scratch.
- You have updated your game client? Delete "Modded_Client" (Shift + Delete) and recreate it.
If everything works*, you have this in your official BnS folder:
- "bin" <- official content
- "bin64" <- official content
- "contents" <- official content
- "Modded_Client" <- the new modded BnS folder
- "Mods" <- where you store your mods
- "Modded BnS folder creator.cmd" <- the script
*If it doesn't work, maybe you need admin elevation to get it working.
Why this script?
I don't really know. I didn't want my official BnS content folder to be NCSofted** by mods, and I can check the authenticity of the installation with the official updater, as the original installation remains untouched. Perfection is satisfying.
Furthermore, as the official installation is untouched, updates and full checks will be quicker. Save you bandwidth consumption, save the world.
**NCSofted means "f*cked up"
What is the weight impact of this "copy" in my HDD or SSD?
It's not a real copy, it's junctions and hardlinks, meaning that the "Modded_Client" doesn't really take up place in your drive. Save your space, save the time, save the world.
Is it possible to change "Mods" and "Modded_Client" paths?
Open the script with notepad, go to the variables part (lines 10, 11, 12).
You'll find AppInstallationPath which is where you BnS client is installed, ModsPath where your mods are stored and ModdedClientPath where your new modded BnS client is created. %CurrentDir% is a variable that means where you script is located.
Where is my umbrella?
You want the script? It's attached to the post.
VirusTotal: www.virustotal.com/en/file/8ae53f42e1c7e245ecee48e62a2907ea3cc2383a9d08c19ae8d5f8ae8eff45aa/analysis/1534071826/


Attachments
Last edited: