Differences

This shows you the differences between two versions of the page.

--- faq:expert [2019/06/29 22:29] – asie
+++ faq:expert [2019/07/20 09:54] – add section on MCP asie
@@ Line 38: / Line 38: @@
 With regards to running ModLoader: No known problems.
+===== Philosophy =====
+==== Why did you create your own mappings instead of utilizing MCP or Spigot's existing mappings? ====
+With regards to the Mod Coder Pack, MCP:
+* MCP's mappings have no clear licensing terms; between the old MCP license ([[https://minecraft.gamepedia.com/Programs_and_editors/Mod_Coder_Pack#License_and_terms_of_use|as preserved on the Minecraft Gamepedia]]) and the new MCPConfig repository.
+    * While other projects like OptiFine and Sponge utilize MCP, redistributing MCP mappings - which is forbidden without explicit permission - is necessary to support SRG-obfuscated mods, something [[https://github.com/MinecraftForge/MinecraftForge/blob/1.14.x/LICENSE.txt#L32-L35|only done by Forge]].
+    * Even if we had been granted permission, it is unlikely that we would be freely able to extend this permission to other developers. This would go against Fabric's core values of development freedom and transparency.
+* MCP's mappings are not always updated to every non-"release" Minecraft version, nor are others generally allowed to do it themselves. This would forbid Fabric from updating to snapshots or other experimental releases.
+    * Additionally, MCP's updating toolchain - as of the last few years - relies on proprietary Mojang information, not accessible to common users, as well as software without clear licensing terms. In contrast, Fabric's updating toolchain relies solely on free software tools (Stitch, Matcher, Tiny-Remapper, Enigma), and the artifacts of the process - just like the mappings - are publicly available.
+* MCP's mappings have an updating process we consider insufficiently open to code review, in our opinion, utilizing [[http://mcpbot.bspk.rs/|IRC bot submissions]] over a merge request system. (However, this is largely a matter of preference.)
+With regards to Spigot:
+* Spigot's mappings only cover the server side and are very incomplete,
+* Spigot's mappings suffer from similar licensing issues as MCP.