User Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
modding:installmodguide [2025/09/01 01:40] – [Add mods] joneirikmodding:installmodguide [2025/09/01 22:34] (current) – [Bloodstained: How to install Mods] joneirik
Line 3: Line 3:
  
 Writing a short guide on how to install mods, and the most common problems and how to figure them out. Writing a short guide on how to install mods, and the most common problems and how to figure them out.
 +
 +If I've forgotten something, or you have suggestions for things I can add, just contact me on the discord. -joneirik
  
 ---- ----
Line 55: Line 57:
 ==== Remove Mods ==== ==== Remove Mods ====
  
-Simple, either delete the .pak file from the folder.+Simple, delete the .pak file from the folder. 
 + 
 +If you have set your windows to show you the actual file extensions (it's off by default, stupid windows), you can rename it so it doesn't end with .pak (for example rename it to .pa ) instead. 
 + 
 +---- 
 +---- 
 + 
 +===== Problem Solving ===== 
 + 
 +> WIP 
 + 
 +Going to add as many problems as I can remember here, and how to try to identify them. 
 + 
 +---- 
 +==== File Conflicts ==== 
 + 
 +Mods changes specific files, and two mods can not change the same file, if they do we get a "conflict" which just means that the game loads one of them an ignores the other. This is also why it's generally a bad idea to add lots of mods in one go without testing them a few at a time. 
 + 
 +There's no real way around this. If you have two mods that changes the same file, and want to use both, you'd have to make your own mod and add the changes from both into the same file. The game can't pull bits from different files. 
 + 
 +Most mods will list which files they modify in their descriptions or readme files, so you can use that to keep track. 
 + 
 +If you have a conflict and don't know which files conflicts: 
 +  * Copy all mods to another folder for backup. 
 +  * Copy 1 mod back at a time and test, repeat until you get a conflict again 
 +  * Remove another mod until the conflict stops 
 +  * In the end you should know which 2 (or more) mods conflict 
 + 
 +Then you can choose which one is more important for you. 
 + 
 +---- 
 +==== Folder Priority ==== 
 + 
 +The game loads .pak files in a specific order (according to folder and file names). I don't remember the specifics of how it works, but files put in the subfolder ~mods will place them in the correct order to override the original .pak files. If you place files in the normal Paks folder they could be overridden by the original .paks depending on the naming for example. 
 + 
 +The short version is always put mods in the ~mods folder, and it will save you a lot of headaches. 
 + 
 +---- 
 +==== Mod Managers ==== 
 + 
 +Many prefers to use Mod Managers, programs to assist the player in installing, removing, and managing mods for a game. I would argue that for Bloodstained it's actually easier to do it manually (following the steps above), but also to avoid certain amounts of problems. Mod Managers generally work but often struggles to do a good job of keeping track of and cleaning up files. So they can fail to properly disable a mod, or clean out files they're supposed to from a game.  
 + 
 +This has led to a good amount of situations where people claim my mods doesn't work, I try to figure out why, and can't replicate it. Until they suddenly realize a mod manager has failed to remove another file that conflicts, or similar situations. 
 + 
 +Different Mod Managers will work in different ways, but most will put the files into your game folders (like Fluffy), so you can solve this by finding the folders and deleting things manually. There might be other mod managers that handles things differently so I can't give a clear solution for all of them. 
 + 
 +In general I'd recommend not using mod managers. If you do use one and experience trouble: 
 +  * Try to disable all mods in the mod manager 
 +  * Then tell it to stop managing the game 
 +  * Then go to the paks folder and clean up everything manually 
 +  * Reset the computer for good measure 
 +  * Start the game and test that nothing remains 
 +  * Then you can start modding manually 
 + 
 +---- 
 +==== Re-Installing ==== 
 + 
 +I've encountered a couple of situations where players for some reason couldn't get one or more mods to work no matter what, ever after all the above. And sometimes re-installing the game solved that. I'm not certain why, but most likely a small fault with the install in some manner or way. 
 + 
 +I'd first recommend trying to Verify Files through Steam or GOG Galaxy. But if that doesn't work I'd try to:
  
-If you have set your windows to show you the actual file extensions (it's off by default, stupid windows), you can rename it so it doesn't end with .pak (for example rename it to -pa ) instead.+  * Uninstall the game 
 +  * Go to the game folder and delete anything remaining (like mods) 
 +  * Reboot the computer for good measure 
 +  * Reinstall the game 
 +  * Start modding again (One at a time, start with the trouble mod)
  
 ---- ----
  

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also, you acknowledge that you have read and understand our Privacy Policy. If you do not agree, please leave the website.

More information