LMD wrote: ↑Fri Dec 25, 2020 14:11
Linuxdirk wrote: ↑Fri Dec 25, 2020 14:03
What's the problem with linking the Git provider's "master" zip file?
1. It requires people to rename the folder (as it doesn't work with the hyphen)
2. It makes people use an inferior method of installation
I disagree.
1. Mod naming hasn't been an issue for a long time, as most mods properly set their mod.conf, so first point is plain wrong I guess.
I think a proper mod.conf should be required, containing at least the mod name, author, dependencies if any, description optional, and...
Now that I think about it, mod.conf should support licensing, that would be nice...
2. As Napiophelios said:
Napiophelios wrote: ↑Sat Dec 26, 2020 03:53
I don't think this is as 'out dated' as you might think.
It's not an outdated method, I still download most mods as .zips, and install them later, even from github, hell, I even download my own mods that way. And I believe many users still do the same, mostly the younger ones, and the ones that use Windows, since it's actually quite easy to install mods this way (one click download, drag and drop to your mods folder, unzip, done)
I agree it shouldn't be mandatory, but as the rule isn't usually enforced is hasn't been for some time, I would say the only thing that is 'out dated' is this rule.
As long as the post provides a proper - and accessible - way of downloading that doesn't require third party apps, jumping through hoops, unnecesary steps, or middlemen, it's alright.
With this said, requiring a mod to be installed via git is not ok, imho, as this would require users to have git installed.