Made a repo https://github.com/Fabulously-Optimized/modpack-creator and we've agreed upon Brancieq first forking and making a feature-complete alternative for current scripts and then, if all goes well, will get full access and contributor :)

A "little" update on the development.

First, what this post will be about: until now, I developed a workflow system, and even if it works, I realized that it's not that great, it would need at least as much working time as what I have provided so far to make it better, and maybe I got the priority wrong.

So I decided to take a step back and summarize my thought here, and explain where I decided the project would go from now.

The following spreadsheet will help you to visualize the explanation:

*: in brackets: potential but need more work

The idea I originally described is too complex and focuses more on the workflow system and concepts abstraction than modpack development, which should be the main focus.

The new idea is to use a task paradigm, a command line tool that proposes different actions, a little bit like FO have multiple scripts.

The basic tasks that apply to all modpacks will be built-ins with the tool, offering a basic way to develop a modpack for beginners. Specific tasks will be addable directly in the modpack project directory. (Examples: the task for updating FO display version, which depends on a specific mod (isxander-main-menu-credits)).

The tasks will be easily configurable depending on the project and the user machine (paths to curseforge and MMC, files to include or exclude when exporting...).

The most important: it will be lighter for me to develop and maintain. It was a bad idea to make a complex thing from the beginning, and I prefer to begin simple, see if anyone uses it and send feedback, use it myself to see what is missing and what is useless, and then improve it if needed.

What's the status of this?

Hey !

So I must update the status of this project. I'll go straight to the point: I think it will never be finished.
I don't think it's impossible to do it. But there are different facts that discourages me:

• I wanted a simple and modular tool. But modularity add complexity.
• The state of the minecraft modding community (Curseforge doing... Curseforge things, Modrinth becoming more and more popular), things change fast, and it's hard to keep up.
• Multiple tools already exist for modpacks, and I find it easier to create a simple script for my own if I need it than creating a new "task", ensure that it work with the tool api ect...
• Finally, the time I don't spend of this tool, I can use it to work on other smaller tools ot mods for my modpack

Sorry for the expectations that I did not meet.

Alright, no problem. If you'd like, you can contribute to the existing scripts to fix or improve something (note the meta issues).