"Signed jars do not make your mod closed source or "proprietary". Signing the jar ensures that it is not modified after being built by whoever compiles your mod (you or anyone else). It's a checksum."
Well I want the ability for the jar to be modified what if a user has to patch a class directly or has to more commonly patch a texture I did this with almost every modpack because of conflicting guis
"Uhm, ok? Then do so."
Can't it's against their eula to have apis or libraries in a coremod which means no coremodding
"Sure, cool. Do that then."
again their new eula states you can only have a coremod in a coremod
"Who is "them"? What are you talking about even?"
Forge's new eula posted on top of the thing right there. I can't do anything can't have apis/libs / regular mod / split the mod up so I can't do anything
"Please clarify where you got this impression from"
Again I read the new EULA
Forge 1.12 and Announcement
"You can overwrite any registry entry"
How since you can't register with the same resource name and you can't remove it. Also if you set the index to null does minecraft crash? My bleep this new forge is a mess why couldn't microsoft/forge just stop in 1.8 when it was already ruined