Make it more clear what fabric.mod.json entries should be replaced

[triphora]

Make it more clear what fabric.mod.json entries should be replaced

[haykam821]

I think a more effective method to reduce license discrepancy would be to emphasize the mod template generator and enable license customization there. Any license discrepancy with the existing mod template in this repository would come from the fact that users are replacing the license file without updating the metadata, presumably from existing license selectors like the GitHub repository creation flow (...though that should be skipped for templates).

Changing the template to an invalid license identifier would just change what these uninformed users leave the license as.

[Levoment]

Agreed. From experience, the users would likely leave the text INSERT LICENSE HERE text in the json file without changing it.

Adding a license dropdown on https://fabricmc.net/develop/template/ could work to mitigate that. Although only to a certain extent if it adds it only to the json and doesn't add the actual license. While adding and maintaining up to date licenses would be a lot of work, adding only the string to the fabric.mod.json file in the generator would help reduce the discrepancies.

[triphora]

In that case this is probably more of a duplicate of FabricMC/fabricmc.net#24. Thanks for the feedback!