Hello. I am taking your and JC's advice - thank you! You'll be able to create the configuration file through KOTORModSync itself.

I gotta tell ya; I've been installing the mod build for about 7 years now. Every couple of years I'd feel like playing KOTOR2 again and installing the mod pack from scratch. I honestly don't know why I don't just keep it installed but you know... life. Never seem to have the same computer either.
I usually mess up one or two steps up on the first try installing the modbuild but after the second I always did it. But this time I messed up three times in a row. Three times in a row. Ugh.
I actually did try to find alternatives to creating this installer. I looked into 5 other mod managers. None of them would be able to support the complex dependencies in the way I wanted. And a lot of them are only compatible with specific games. I mean how can you call your project a 'mod manager' if it only supports Bethesda?

The main goals of this project are to provide a more stable, efficient, and faster way of testing mods. All while creating a configurable instructions file that is easy to share. Leaving more time for actually developing the mods themselves. Perhaps my some of my old favorite mods will be compatible on my next playthrough. I'd still love to see the mod that gives Kreia the mechanical hand on Nar Shaddaa compatible with the build.
I'm not sure how to handle the user interaction with the program in regards to installing the mods itself. At the moment, I have a console app where users can run move, delete, and execute file commands. After a user executes one, it's appended to the config file. This is what I'm working with for testing currently.
We can always add a user interface for dragging and dropping files later.

I hear what you say about the time-consuming work you do to create the modbuild Reddit post. So why not have the program generate some of the content there for you? The config file has many fields describing each specific mod's characteristics. Such as name, description, dependencies, and instructions. Using the program to install your mods would generate documentation and a sharable config file. It'll keep track of your installation, while you're installing it. The documentation would become formatted automatically. I already have a project that utilizes the auto-docs code here: https://github.com/basnijholt/adaptive-lighting
We can just borrow. The entire readme of AdaptiveLighting self-generates anytime we change the code.
GitHub
GitHub - basnijholt/adaptive-lighting: Adaptive Lighting custom com...
Adaptive Lighting custom component for Home Assistant - GitHub - basnijholt/adaptive-lighting: Adaptive Lighting custom component for Home Assistant
GitHub - basnijholt/adaptive-lighting: Adaptive Lighting custom com...
I do realize it's a bit early to be talking about extra features when I don't even have a working version yet. But after 20 years people are still modding Kotor and that's as good of a reason as any to create this project. Even something like TSLPatcher is still used, unchanged from the last 10 years. The community is insane! I'd love to get into the whole modding scene I just seriously wish I had the time...
Life's too short. I'm flown into my hometown in Iowa for family reasons and I have a bit of extra time to do something like this. And I can only handle so much Juhani at a time.
Anyway, because of this I'm focusing on the core structure of the project. A structure that's written in a way that others can add extra features if they like.
This project is open source. Users will be able to submit their own features, such as the drag & drop ui I described, and everything else.