comp500
comp500
Yeah, I'd probably implement some sort of version range system.
Probably quite a while; my time is limited right now and the packwiz-installer changes are highest priority.
Git line ending conversion invalidates the hashes, see https://packwiz.infra.link/tutorials/creating/git/ for how to disable this.
I think currently it doesn't check the name at all, only the slug.. yeah I think it'd be a good idea to check the name as well. I think it'd...
The reason the file name gets overwritten is because the file name from CurseForge might change when updating, usually from something like `mod-1.0.0.jar` to `mod-1.0.1.jar`. I'm not sure how exactly...
Sure, but what if the user renames the file, say to `accurate-block-placement.jar`, should that just get overridden when updating?
Oh yeah, I like that! I probably won't end up splitting it into `filename` and `filepath`, just modify the file name at the end.
My plan for this is really the opposite; I want to get rid of index metadata as much as possible for various reasons (code complexity, hash conflicts, version control churn)....
Oh yeah, a list of added/updated/removed mods and loader/mc version changes would be good... should I incorporate Git commit messages as well, or would that be extraneous for most packs?...
It probably wouldn't generate a changelog, as I don't particularly want to reimplement a VCS in packwiz. I guess it could cache the last exported pack metadata somewhere, but it...