Traister101

That’s on the dev end of things but yes. Part of the build pipeline was re-obfuscation of your code so it’d actually work. Forge the mod loader just loaded the mods and provided code for modders to use. Forge Gradle was what handled the obfuscation stuff in dev

Congratulations you’ve discovered that Mojang used to ship the game after it was obfuscated! Java has nothing to do with the fact it’s obfuscated that’s on Mojangs end, for goofy “This’ll allow us to sue people who copy our game” logic. NeoForge came out the gate with official mappings at runtime (non obfuscated using the offical names Mojang provides. Yes Mojang obfuscated the game and then gives us the names of stuff anyway…) and recently Mojang announced they are finally dropping obfuscation all together.

Edit. To make sure this is totally clear the obfuscated names such as class_5699.method_65313 is the actual class name and method name. The jar has a class named class_5699 which Java loads and treats like any other class. Very goofy and annoying for modders since if you wanted a useful name you have to first decompile Minecraft, then change all the names, and then when you compile change all references to said names in your code back to their actual obfuscated nonsense.

Neither did Log4j in basically all cases, some maniac just put arbitrary code callbacks into their logger, undocumented and enabled by default. The insane part isn’t the feature itself it’s the fact it’s enabled by default in a logger of all things.

People in my experience are actually very serious about the standard out to debug log which is… baffling. Same people generally outright refuse to learn how to use a debugger in languages where those are pleasant

A logger? Console prints are shitty in general but especially when you have an actual logger already

It can. It depends on what changed. If both of you touch the same file in a conflicting way you’ll have to merge the commit with the conflict. If you don’t then it just auto magically works.

For example if you have commits A - B - C with a branch A - D with D adding a brand new file you can trivially rebase (IE no need to merge) D onto C for a history of A - B - C - D

The best part about rebasing imo is that you get to merge commit by commit. Using the previous example if there’s a conflict in commit B but nothing in C all you have to do is fix commit D to handle the changes B made, nothing else

Very true the last ones weren’t going around spewing as many Nazi talking points

Because it sounds like English words which is “cool”

95% of the people in a dictatorship like the dictator! That’s crazy