IMPORTANT NOTICE: I've got a new entry for the mod manager on NexusMods. If you want help using it, you should go to the post section for the new NexusMods entry: https://www.nexusmods.com/site/mods/818?tab=posts
Since it seems that no one got a better solution, here. Fluffy is installing the .pak files in the same folder as the exe, so you can you create a BloodstainedRotN.exe dummy file on the ~mods folder and set that as the game's directory. Done, fluffy works now. The only downside is that you can't launch the game from fluffy but that doesn't really matter.
Also I found the reason, if you throw the .rar/.zip in the mod manager, it installs in the same place as the exe, if you throw the .pak by itself, it actually installs on the proper folder
can this be used with mods with a .pkg extension? I have a mod that says to use this with it, and while it shows up on the manager screen it won't appear in-game
HELP! I know I'm not alone, a lot of other people have said they are having this bug! The mod manager is the LATEST version, and yet the mod manager is installing my mods in the wrong location.
Where it is currently putting them: (Something weird, notice how the slashes are FORWARD slashes... but not BACK slashes? That seems odd to me) ..steamapps/common/Bloodstained Ritual of the Night
Where they need to go to work: ..steamapps\common\Bloodstained Ritual of the Night\BloodstainedRotN\Content\Paks\~mods
I have gone into the Options > Define Game Info > Install Path.. and tried and tried to properly define where I want the mods to go, the Mod Manager throws back an error. "Invalid or missing install path, try to automatically acquire it.."
I can see exactly why my Mod Manager is putting them in the wrong place but it's being stubborn, what do I do?
I do indeed <3 And when I physically move all the mods they all work beautifully. But that's the problem, the Mod Manager refuses to change the Install Path in the "Define Game Info" section of the Options!
I really really want it to be in: ..steamapps\common\Bloodstained Ritual of the Night\BloodstainedRotN\Content\Paks\~mods
But the manager keeps throwing that error at me, and stops short in the Wrong Location! I'm so confused!
Currently, as of January 17th 2021, my version of Fluffy Manager 5000 re-allocates manually-implemented mods to the same directory as the executable, unlike the in-app mods; those create the exact same folder path to mods. To note, the following mod I'm using as an example is not packaged in a RAR file; rather, it's in its own folder, laid out in the following manner:
• Fluffy Manager > Games > Bloodstained > Mods > Max Stack Plus >> MaxStackPlus.pak >> modinfo.ini >> screenshot.png
It's troubling to see this happen, to say the least. I'm using Windows 7 Pro, 64-bit architecture. I've tried running the program with admin privileges, compatibility modes for Windows 7, Server 2008, and Vista SP2 to no avail. As of right now, the only possible workaround I could have is copy-pasting the game executable into the ~mods folder and define the path there via the program. It's a dirty solution, but it's all I currently have. Another acceptable solution is to have an empty .txt file renamed to the game executable name, and changing the extension to .exe.
I do hope that you can find whatever is happening that's making this happen, even if you're not affected by it. Somewhere in the middle of all this, there has to be an answer...
Try putting just the PAK into the mods folder. Bloodstained support works differently than other games in the mod manager (and I might have done a poor job explaining that in the documentation). For Bloodstained, the modinfo.ini and screenshot should be compressed into the root folder for the PAK archive.
Just the PAK works fine, and the program adds and removes the PAKs as needed, doing what I assume is intended by copy-pasting the files in question into the program. It's just the rerouting that isn't working for some reason, which is odd.
Ah, well, I'll handle it with the actual PAK maker, see if that makes a difference. 'ppreciate the attention all the same.
If I may interject - perhaps you could apply a method to batch-install/uninstall all mods that fall within a category of sorts? Or, perhaps even add a new variable to modinfo.ini recognizable by the program called 'group'? Functionally the same as 'category', but exclusively for the aforementioned suggestion.
The mods install in SteamLibrary\steamapps\common\Bloodstained Ritual of the Night folder instead of the contents/paks folder, I still need to manual drag in the mods to get it working
I tested this and it doesn't happen on my end. You should try using latest WIP version (http://fluffyquack.com/WIP/modmanager.zip), or ensure mods are stored as PAK rather than compressed into RAR in the mod manager itself.
As someone else has said, it seems like the manager drops these files in the top folder where the exe is instead of the ~mods folder. It does not do this for any other game. Is there anything I can do to adjust this?
In the meantime, can you check if the latest work-in-progress version does this too? http://fluffyquack.com/WIP/modmanager.zip
Edit: I tested this and it doesn't happen on my end. You should try using latest WIP version linked above, or ensure mods are stored as PAK rather than compressed into RAR in the mod manager itself.
Give Feedback
34 comments
Fluffy is installing the .pak files in the same folder as the exe, so you can you create a BloodstainedRotN.exe dummy file on the ~mods folder and set that as the game's directory.
Done, fluffy works now. The only downside is that you can't launch the game from fluffy but that doesn't really matter.
I've just downloaded the game, and would be great to have a mod manager.
You extract the mod manager anywhere, run modmanager.exe, choose Bloodstained as game, and drag'n'drop PAK files onto the mod manager.
You might want to download the latest version of the mod manager from here: https://fluffyquack.com/tools/modmanager.rar
I can't remember what version I had uploaded to this page, but it's probably a rather old one.
Where it is currently putting them: (Something weird, notice how the slashes are FORWARD slashes... but not BACK slashes? That seems odd to me)
..steamapps/common/Bloodstained Ritual of the Night
Where they need to go to work:
..steamapps\common\Bloodstained Ritual of the Night\BloodstainedRotN\Content\Paks\~mods
I have gone into the Options > Define Game Info > Install Path.. and tried and tried to properly define where I want the mods to go, the Mod Manager throws back an error.
"Invalid or missing install path, try to automatically acquire it.."
I can see exactly why my Mod Manager is putting them in the wrong place but it's being stubborn, what do I do?
Do you have the mods stored as PAK files in the mod manager?
I really really want it to be in:
..steamapps\common\Bloodstained Ritual of the Night\BloodstainedRotN\Content\Paks\~mods
But the manager keeps throwing that error at me, and stops short in the Wrong Location! I'm so confused!
executable, unlike the in-app mods; those create the exact same folder
path to mods. To note, the following mod I'm using as an example is not packaged in a RAR file; rather, it's in its own folder, laid out in the following manner:
• Fluffy Manager > Games > Bloodstained > Mods > Max Stack Plus
>> MaxStackPlus.pak
>> modinfo.ini
>> screenshot.png
It's troubling to see this happen, to say the least. I'm using Windows 7
Pro, 64-bit architecture. I've tried running the program with admin
privileges, compatibility modes for Windows 7, Server 2008, and Vista
SP2 to no avail. As of right now, the only possible workaround I could
have is copy-pasting the game executable into the ~mods folder and
define the path there via the program. It's a dirty solution, but it's
all I currently have. Another acceptable solution is to have an empty
.txt file renamed to the game executable name, and changing the
extension to .exe.
I do hope that you can find whatever is happening that's making this happen, even if you're not affected by it.
Somewhere in the middle of all this, there has to be an answer...
Ah, well, I'll handle it with the actual PAK maker, see if that makes a difference. 'ppreciate the attention all the same.
In the meantime, can you check if the latest work-in-progress version does this too? http://fluffyquack.com/WIP/modmanager.zip
Edit: I tested this and it doesn't happen on my end. You should try using latest WIP version linked above, or ensure mods are stored as PAK rather than compressed into RAR in the mod manager itself.