-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for more project types #141
Comments
This would fit in more with v5, where ferium would ideally become an entire launcher. For now ferium remains a mod manager and this issue will be in the backlog, it will not be a priority for now |
By launcher do you mean it would become it's own application? Cause if so I like it better as more of a terminal/command line type of thing rather than an application launcher. Especially with this project under the same group making GDLauncher |
I had initially been thinking of an alternative GUI frontend, but I think it's better that I purely focus on the CLI experience. So yeah a launcher expansion would most likely be CLI only. |
If/when ferium becomes a launcher would it still work as purely just a mod manager? |
If you're asking if you'd be able to use it only for mod management, and use something else for launching the game, then yeah absolutely. |
If/whenever you decide to add it do you know if it would work similarly for resource packs and shaders as it does for mods? Or if there's going to be a complete rewrite of how it works? I'd get it if it's too distant in the future to tell yet Also if mod management would work the same way it does now or if that'll change? |
Yes, mod management would work the same way, and as would any other project types too like resource packs and shaders. There most likely won't be a rewrite of the mod management. |
Support for managing resource packs and shaders would be extremely helpful, and in my opinion, would fit in with Ferium.
This would add some complexity to setting up a profile however, from having to specify the shader and pack output folders, but making it optional and only required once the feature is used would be a good compromise.
Thank you to all the contributors <3
The text was updated successfully, but these errors were encountered: