How It Works NOTE: I threw this together in 30 minutes, so it requires testing. Consider this an early version
The basic idea is that you download an entire modpack split into zip files and this tool extracts them and fixes file paths. That's it.
Why this vs Wabbajack
It's easier to just download an entire modpack and have a tool do minimal steps to extract it than have to download a million mods from Nexus and have Wabbajack be a middle man through that entire process. **** the Nexus ******, just zip it up
To Do
Do more testing on what else is needed
Add an Export tab, that turns your MO2 instance into game folder files
ㅤ
Fix file pathing when editing ModOrganizer.ini
Auto-add rootbuilder plugin to the paths
Ignore __pycache?
Reporting Bugs
To report any bugs, please submit a post in the Mod Support section and mention my username.
I'm interested because I use Linux which makes Wabbajack a pain, but I'm missing something:
It's easier to just download an entire modpack and have a tool do minimal steps to extract it than have to download a million mods from Nexus and have Wabbajack be a middle man through that entire process.
I thought automating "Downloading an entire modpack" was the overwhelmingly more important part of Wabbajack - it does the job of clicking 1800 Nexus links and downloads. **** doing that manually. So if this is meant to be "the lazy man's Wabbajack", how is that going to work?
I thought automating "Downloading an entire modpack" was the overwhelmingly more important part of Wabbajack - it does the job of clicking 1800 Nexus links and downloads. **** doing that manually. So if this is meant to be "the lazy man's Wabbajack", how is that going to work?
The basic idea is we make our modpacks and then just share the MO2 instances with each other, not the process of installing it (which is what Wabbajack automates)
The only reason Wabbajack is so convoluted and unreliable is because Modders get crybaby ****** when you reupload their stuff, so Wabbajack "has" to redo the entire installation process every time
Last edited by loregamer on March 12th, 2025, 18:07, edited 2 times in total.
I thought automating "Downloading an entire modpack" was the overwhelmingly more important part of Wabbajack - it does the job of clicking 1800 Nexus links and downloads. **** doing that manually. So if this is meant to be "the lazy man's Wabbajack", how is that going to work?
The basic idea is we make our modpacks and then just share the MO2 instances with each other, not the process of installing it (which is what Wabbajack automates)
The only reason Wabbajack is so convoluted and unreliable is because Modders get crybaby ****** when you reupload their stuff, so Wabbajack "has" to redo the entire installation process every time
But what if you want a modpack that no HQser has preassembled yet and thus have to download fresh?
Fkn Wabbajack been pissing me off something fierce, I've been fighting with it for over a month and would love to just move right past it, this seems like a pretty good option
Fkn Wabbajack been pissing me off something fierce, I've been fighting with it for over a month and would love to just move right past it, this seems like a pretty good option
Just being able to backup and restore my whole modlist quickly is a hell of qol improvement
I haven't maintained this because I learned that backing up a Mod Organizer 2 instance is way easier than I thought. All you have to do is zip everything up in the folder except for the ModOrganizer.ini file. You then share that zip file with others. When they launch ModOrganizer.exe, it'll launch the instance as the "first time", and do the necessary steps and whatnot.
I guess I could update this, but it'd just be changing it to unzip MO2 and then unzip the backup ZIP after
Last edited by loregamer on August 16th, 2025, 12:46, edited 1 time in total.
Easy MO2 Installer 
