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
Pack import fixes and improvements #1563
Conversation
Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
Signed-off-by: TheKodeToad <TheKodeToad@proton.me>
wouldn't not selecting a mod = not downloading it make more sense? this behavior is kinda weird. Apart from that this pr seems fine |
Well not really: If you would want to add them later how would you know what mods need to be added and what version?
Also the previous implementation the mods are always downloaded but they are disabled if they are optional. |
https://docs.modrinth.com/docs/modpacks/format_definition/#env-optional The modrinth docs seem to prefer the behaviour I mentioned (which is honestly the one which makes the most sense to me and it's what launchers that have this option do, and what we do for atlauncher packs) honestly it doesn't make much sense to have the page if you're still gonna download it but disabled anyways |
I think it's nice as it allows the user to review the mods which will be disabled by default |
In the documentation, I do not see anywhere how should I handle the unselected resources(doesn't say that I should not download them).
All of them download the optional files. |
I assume in the case of Modrinth it is either unimplemented or a bug :P |
Maybe we should stop checking extension and just add |
I thought that was something modrinth does, on flame there is no such check. |
Not necessarily in this pr - but resource packs etc. can also be optional |
Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
Signed-off-by: Trial97 <alexandru.tripon97@gmail.com>
hey @Trial97 , I like the pull request, but I think something like |
Hi @nopeless, |
No, and I doubt there will be any collisions unless the filename is unicode (which is very unlikely either) However, I don't see why the regexp has to be so restrictive either. If it needs to be filename safe, then the regex should show that intent. At the very least, I think you should add a space to the allow character list so spaces are preserved for easier reading in case of a need to debug. |
Or I may have misread the code I'm assuming |
That name is precisely only used when we import the pack to give the name of the icon of the pack, nothing else. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
everything seems to work in my testing.
this "Create Extra" pack from mr confused me a bit as it seems to put a lot of libraries like fabric API and fabric language kotlin, etc. as optional. But I guess thats just how it is..
It seems a bit odd to me, but I have to assume its just the pack making weird choices in what should be optional and what not...
UNLESS thats something coming from prism due to some dependency resolution stuff that needs to be considered here? thats just how the pack comes, imma merge
Multiple fixes and improvements regarding pack import:
\
with/
in the file path for modrinth export (this pack: https://modrinth.com/modpack/another-rpg-pack failed to correctly install because of this)