- Joined
- Sep 16, 2018
Forge also has a habit of getting anal at you for deciding to do things in any way that isn't "muh Forge way" by either discouraging or outright barring you from using vanilla's own systems.I've messed with Minecraft modding before on both Fabric and Forge, and Fabric is just a lot better to work with in general no matter if you mod or develop. Forge is a general ass to deal with as a developer, and Fabric feels better supported, more stable, and easier to make things compatible. It's also pretty lightweight, while Forge needs a progress bar just to tell you it's loading.
Funny how competent people make better shit.
Want to register a block or item on Fabric? Just call vanilla MC's registration methods on an instanced Block or Item at any point within your code and you're basically done as long as you have the right registry. Happy days. Want to do it on Forge? You have no choice but to either relegate it to their own registration event or go through with retarded bullshit like a DeferredRegistry and instantiate not an actual block or item, but a "RegistryObject" which is nothing more than a glorified Supplier, every single time.
Anything that vanilla MC / Fabric can already do just fine with only however much boilerplate vanilla decided to have in place, Forge will have absolutely come up with a convoluted, overengineered hunk of dogshit that has like 30% more boilerplate for only half of the usability or versatility that the existing stuff already had. Don't get me started on the existence of Forge's LazyOptional either, that thing is the absolute spawn of Satan's asshole.