Why are there so many Modloaders? || (Forge, Fabric, Quilt, Neoforge)
HTML-код
- Опубликовано: 26 дек 2023
- Want more? Check here...
=Socials=
Second Channel: @LunarVods
Twitter: / cygnus_mc
Discord: / discord
Want access to the full interview and support my work?
Join the Patreon: / cygnusmc
Thumbnail by: @gutermaniac
Pebble art by: midnightmorpha.carrd.co/
=Summary=-
In the beginning of its history, Minecraft had Forge, the one big modloader. Now we have Forge, Neoforged, Fabric and its fork Quilt, all dancing around eachother in a complicated dance while completly ignoring eachother.
#forge #minecraft #fabric
=Timestamps=
None
=Credit&Sources=
Footage by ItsDrowned
/ itsdrowned
Music provided by Infraction No Copyright Music
Spotify: spoti.fi/3DzsedZ
If You've Read This Far Comment Pebble :) 
Игры
Whatever Modloader you use, i still love you ❤
Shout at me in discord: discord.gg/cygnusmc
CORRECTIONS BELOW:
Apearently, Quilt has been allowing farbic from the start, however i personally have had fabric mods crash on me on Quilt. But fabric should WORK on Quilt!
Ive also recieved a few comments saying i should have covered why quilt split off, however as someone who has 0 experience to do with anything that caused quilt to split off i dont feel like i could do it justice. TLDR there are alligations of the (Lead?) dev of fabric beeing transphobic and generally unpleasant, this caused quilt to split off.
That beeing said, Trans rights!
Awe 🥰
i dont love forge users /j
Question : "Why are there so many Modloaders ? (Forge, Fabric, Quilt, Neoforge)"
Answer : Because MOJANG is too busy working on adding sniffers, breezes and armadillos, instead of focusing on creating an official modding API (an API that is backward compatible to make life easier for modders), and a minecraft built-in Modloader that could replace every other Modloaders...
neoforge has up to 1.20.2 in stable and 1.20.4 in unstable
Cygnus I agree with what you said because I believe that no one should uh bully or shit on others who use preferred mod loader(it seriously annoys me lol)
The NeoForge devs are very much working closely with the fabric folks, they are not ignoring the other modloaders. NeoForge is a great step in the right direction, fabric will improve as a result as well.
The ignoring part was more in the way of not allowing eachother to run on eachother
I think it sounds reasonable to not have that kind of compatibility, sometimes supporting features like this can be a larger task than the original codebase. That being said, there’s a couple of projects out there which produce mods that do this to an extent, which I think is the correct approach to the issue.
I’m happy the modloader teams are communicating, as that seems like a really positive thing that should benefit everyone.
@@kiweezi so am i! But from what i can see, its only Quilt and Neoforged who are talking
Sinatrya Connector is funny since it allows fabric mods on forge
@@walksanator it causes issues within the forge env and the fabric env
while loading fabric mods on forge, is a downgrade of performances and features
For me personally it just boils down to which version my favourite mods are. I cannot say the difference in optimisation between loaders is significant enough for me to not want to play without particular mods
same, Fabric runs well, but not well enough for me to abandon my favorite mods!
i notice no difference on forge vs fabric without any optimisation mods
Yeah totally agree, it used to be pretty drastic how slow Forge was especially in the 1.12-1.16 days with the startup time, but I think in 1.19 and 1.20 it's improved to the point where it doesn't matter
I use them all. It really just depends if there's a cool mod(s)that I want to use for a server with my friends
@@ziggybadans there are now mods that decrease the start time from versions 1.12.2 to 1.16 in forge significantly
As someone who makes personal modpacks with over 200 mods, and sometimes over 250, all of which I download and test manually, I do understand your struggle.
Same. Tho worst part is putting them on aternos. I don't have money to run good server so yeah aternos it is.
For me what might work in single player might crash aternos and there's also limit to how many mods like memory usage can be in server. And you gotta check them one by one check their version import version if it happens to not work you need to change version both on your modpack and aternos mod list.
@@radiostoneworks9290 idk, for me personally I never had any real trouble with adding the mods to a server since I self hosted one with a server.jar file, but I can’t imagine why adding mods to a world would break when switching from single to multiplayer since Minecraft’s change in 1.3.1 to have the code for both become merged.
@@ocks_dev_vlogs problem is that in aternos you have to add mods one by one. So you have to check 100-200 mods all over again. Check if they are client only server only or both. Check if aternos even have them or not. Some mods are unable to be used in aternos tha happens to so sometimes I have to rework part of my modpack again.
@@ocks_dev_vlogs and breaking of stuff happened when I tried to figure out one vampirism addon.
Small correction - Forge is not the oldest modloader. There was, infact, a 4th modloader that predated forge by a good while. It didn't have any official name, iirc, it was simply just called "modloader". It has since been completely abandoned, with forge coming in after to replace it, and so forge has been the standard for years after. Fascinating video, otherwise!
ModLoader is its official name
Risugami's modloader.
I used to use it waaaaaay back in the day. As I recall, the API was abandoned due to CPW building his own version of the modloader functions on request of Slowpoke101 of Feed The Beast. Prior to this point, Forge actually relied on Risugami's modloader for basic functionality, however since Risugami had revoked permission for Slowpoke to redistribute his modloader as Slowpoke violated the API's license.
As a result, Risugami sort of gave up with his API, since Slowpoke was now actively pulling modders away from Modloader by telling them "Your mod won't gain any popularity unless it's in my modpacks. And you won't get into my modpacks unless you use Forge instead of Modloader"
Risugami's ModLoader :)
The last time I modded minecraft and had any idea what I was doing, it was during the time of ModLoader. By the time Forge came out I was like "what is this this is complicated I don't get it" and now look where we are
@@lovelydumpling when forge came out it was just another mod you had to install after modloader
The existence of 4 different modloaders provides multiple benefits for developers and zero for users.
Since there are multiple implementations with different design philosophies, developers can just pick whichever suits their workflow best. This is something that very much helps to expedite mod development.
However, mod users don't see this benefit. All they see is an arbitrary choice they have to make. There are attempts at improving cross-loader compatibility but they're generally pretty hard for developers to work with.
Overall, I don't think it's a straightforward problem with a straightforward solution.
Even for developers with a small team or solodevs are not too fond of the split. Yung has made his own compiler that compiles for both fabric and forge, but smaller teams dont have the time or resources to do that
The actual solution is quite simple, really:
Native modding API directly from Mojang, allowing for all sorts of stuff and probably combining all the benefits of both Fabric and Forge
However, it's probably not gonna happen anytime soon if at all considering how long it's been since its announcement and how it was eventually postponed forever
@@AltPlus30 The general sentiment I see among modders is that community-made modloaders are universally better than whatever Mojang would have given us. Mojang's loader probably would only allow for mods that add new blocks, entities, and items, similar to datapacks
@@pencilvoid yeah considering Mojangs history. Its sad that too this day basically the only games that have actual first party modding support are Bethesda Games. To be fair they sacrifice quite alot for it in flexibility of their engine but its modding capabilities are peerless.
@@Cygnus_MC It depends on the developer. Developers are entirely within their rights to ignore users asking for ports. If a developer chooses to care about users asking for ports, well, that's their decision I guess.
Developers can now use the Architectury API to write one “piece” of code that can run on all loaders which Architectury supports. This reduces the time needed to port mods to other loaders because the developer only needs to write once and the code will work everywhere magically.
Yes, i think Yung uses this. However some things are just very different in between the modloaders, so not all devs can use that
@@Cygnus_MC actually I’ve developed mods using Architectury and it’s more simple than you think to solve differences in the mod loader because the Architectury API is common between all loaders, internally the API is implemented differently for each loader.
In addition the API allows you write code for certain loaders if you need to, for example integration with Forge Energy could be done only on Forge. This is because projects are still separated between loaders.
For example the Minecraft Transit Railway’s source code has a “common” folder, a “fabric” folder, and a “forge” folder. The common folder contains most of the mod (like blocks) and the “fabric” / “forge folders contains initialisation and some mixins.
@@samuelhulme8347 Wait, if FE can't be used on fabric, then what do they use instead?
@@widmo206 FE of course, it stands for Fabric Energy (This is a Joke)
In all seriousness most mods have different energy systems and some mods are made to be compatible, some aren't
I can't believe we got to the point where we're basically writing C again for MINECRAFT MODDING of all things
For anyone struggling with keeping up (like me!), I suggest using a custom minecraft launcher like prism, where you simply select the mod / mod pack you want, and it handles the rest.
Fabric has been a massive game changer, dramatically reduces server costs for me and mods like sodium are genuine magic that make optifine seem like a sick joke. Additionally, I don’t think it’s a coincidence that modrinth was released around the same time.
I agree that it’s annoying having to deal with more modloaders, but I believe that so far it has been a net positive.
By all means, this is a great solution!! I should've mentioned it in my video itself. However it still leaves some player out of the boat. Not to mention developers themselves, Yung mention in my interview with him that he has a specially made compiler that can turn his code to work on both. While Speiger and smaller teams either dont develop on fabric due to it not having the same methods or at the time even missing methods they need to make their code run
@@Cygnus_MC i as a dev. If i am willing setup architectury which is a multiplatform library. I just write some code that needs to be usable everywhere. And if i need platform specific things, then i can just @ExpectPlatform and it just works
@@Cygnus_MC Thanks! Totally agree it's not a comprehensive solution and as with most things in this area, it's not very accessible to the average user.
People who just want to install premade mod packs or random mods to mess around with and don't care too much won 't be affected. The people who are affected are people who have a very specific vision for what they want to turn the game into, however half of the mods they need are not compatible with the other half.
@@snark567 mixin conflicts 😔
2:44 I think one thing thats missing from that choice is that mod developers, especially developers who were established in forge for a while, were already used to porting MASSIVE parts of their code because forge kept changing up its API every goddamn minecraft version, the result of which caused many mods to die or straight up be completely different experiences because porting the old code to a new version was basically a herculean task, so the people who have survived through that had the choice to risk forge doing it again and forgetting to write proper documentation for potential years or go to fabric where one of their main goals was wanting newer mods to work on older minecraft versions, so its not so much "port the code over" but "port the code over one last time". And seeing as mods like botania took only a month or two to port to fabric while waiting for a new forge version and create seems capable of keeping parity pretty easily, i doubt mod developer size matters all that much when forge docs are just that awful at keeping up with their own features.
Fair point! However as speiger and other developers have mentioned to me, fabric doesnt have all the tools forge has, or atleast not to a standard they would be happy with. There are however, most definitely people who did port over to fabric to be done with forge's api updates!
Fabric mods don't work on older Minecraft. You might be thinking of Sponge or Bukkit.
@@thewhitefalcon8539Sponge and Bukkit run plugins, not mods. Fabric is a mod loader but it also can be ran as a server, but it primarily to the average user a mod loader and this person is talking about mod loaders and not server variations.
@@thewhitefalcon8539 Their actually is a version of fabric for older versions, it's called legacy fabric.
@@thewhitefalcon8539You can run 1.20 fabric mods on 1.16, at least the simple ones, if something depends on a feature in 1.20 it wont work tho
While I greatly appreciate all the work the devs of these loaders put in, from a user standpoint it gets very frustrating and confusing when I just want to play with the mods I want. I cant rlly complain much tho because they’re doing a service creating all these mods and loaders.
Im a user and a modder, and very much understand your point, as I create my own modpacks. But, you should understand (im not saying you dont), that the majority of modders dont get money of their work, and do this for fun.
I try to appreciate that modders even do modding on the first place, becuase it's very time consuming and doesn't usually pay off financially.
@@nicocraft31 That is the sad part of it, maybe if we could make another way to monetize and help devs would be good!
I agree
4:35 it's not only "now", Quilt Toolchain always provided Quilted Fabric API, which always allowed to load Fabric Mods
Pretty sure at one point they didn't, atleast i personally, and others have not had succes running fabric on quilt. Some report fabric mods working but beeing broken, but now it seems stable
@@Cygnus_MC quilt was always intended to run fabric mods, earlier builds struggled with compatibility but basically everything has been able to run for over a year now
@@bonkerbonk343 is quilt dead? i mean they didn't update the quilted fabric api in ages
@@Cygnus_MC That could be caused by the fact that some fabric mods deliberately included code so they didn't work on quilt. I was at least never aware of any problems originating from the quilt loader. However, I might not be a fully reliable source given that I was on Quilt's decompiler team and wasn't really involved with it's other aspects - I eventually left in protest over some insignificant issue, so I cannot be a reliable source for anything modern-ish (i.e. the last 10 months or so).
@@geolykt ive recently had the privilege to talk to the original developer and they did admit that there was a point early on fabric mods didnt work
As a 1.7.10/1.12.2 mc enjoyer I'm so glad I don't ever need to deal with this drama
Fabric on this version would still enable a lot more mods. Trust me I used to mod it.
@@thewhitefalcon8539 Yet there's few of the mods updated from 1.7.10 to the newer versions so no thanks.
@@Foxx33 I mean fabric on 1.7.10
@@thewhitefalcon8539 There is Fabric legacy. You can mod Minecraft 1.3 with it if you really want.
@@thewhitefalcon8539 there is no fabric 1.12.2 or 1.7.10, i cant find it
its possible quilt didnt allow fabric mods at the time because the slight changes they made to their mod loader could have a chance to possibly cause issues with fabric mods, so would probably want only mods made for quilt to work before trying to add support for another mod launcher (even if they are very similar)
im almost sure its that
Quilt has always supported Fabric mods, not sure where that idea comes from
@@GarethC Quilt said that it may not work with fabric mods in the future on the website (around aug 2022 I guess since I commented on that in AOF discord back then) but didn't actually follow though, which caused that misconception
@@ssdrbx6180 Yeah I know, I was a community manager at the time - the point was that someday it might not be something Quilt devs may be able to reasonably do on their own anymore, but there was never a set date or anything
@@ssdrbx6180 yeah, I was quite confused. I remember when Quilt started to show up, it seemed more to me like a variant of fabric and it seemed to work fine with other fabric mods.
I still remember when Risugami's modloader (Which I only knew as modloader for a huge amount of time) was the only one available, and Forge was the new thing, truly a magical time, nowadays it's weird
Forge was an addon to modloader. Modloader had the basic mod loading while forge had all the invasive hooks.
and Eloraam was basicly hording forge to turn it into a coremod for her own pet project, spooking off Flowerchild and kickstarting the Better Than Wolves drama
Well, gotta add my bit here with source being "Trust me bro".
To my knowledge, Fabric was never intended being a competitor/rival to Forge, but rather an alternative. Main idea of Fabric is being lightweight and encourage modders to make their own tools if API is unable to provide them (i.e. Fabric API does not have any API for configs and there are no plans to add one, reasoning this that there's no good variant that could satisfy everyone), while Forge was aiming to be one giant toolbox of everything you would ever need, but very much trying to restrict devs manually to its API and libraries.
And speaking of modloader that actually supposed to be straightforward competitor to Forge and promoted itself as replacement for it, Rift is the one. That weird thing that popped up during 1.14 and instantly died. And ironically, it died due copyright claim from Forge team due dev(s?) behind Rift using some other project that belonged to Forge team or some of its members and wasn't free to use for everyone.
But again, that's what I heard somewhere across different sources, so don't quote me on this. I'm just also the person who had banged their head on the wall enough trying to find the answer on the amount of modloaders for this game
P.S.Adding on Quilt... All drama aside, it manually attracted people who weren't able to find place for themselves in neither Forge or Fabric communities. And I prefer to vision it as some sort of an experimental playground, since as I've seen it was the least restrictive in terms of which ideas can be added to the project in compare to Forge and Fabric
> while Forge was aiming to be one giant toolbox of everything you would ever need, but very much trying to restrict devs manually to its API and libraries.
While that is somewhat accurate. Bypassing forge and directly interacting with minecraft is easily possible with forge.
It is just that forges toolset and features are just that convenient that devs choose to stay within forges guidelines.
Just to give a bit of examples:
IC2Classic, a huge mod bypasses a TON of forge systems and works with vanilla directly because it is for us a lot easier to do so, mainly due to scale, and me only wanting to deal with some of forges BS.
But we still use a ton of forges systems out of convenience, because they make a ton of things accessible that you manually have to implement into fabric.
Just wanted to append this because it is not quite as simple as "forge locks things down and fabric gives devs 100% control", because it isn't as black and white.
@@Speigeras of current situation, that's true. But to my knowledge Lex was very much against such stuff as mixins before Fabric shown how beneficial it can be. That's why I used "was" here
@@Nord_Act Oh yeah i am fully aware. I know cases where lex has banned people for mentioning asm. xD
But for 95% of the cases mixins were not required for what we did. It was simply avoiding forge systems directly and used vanilla systems instead or wrote our own.
Its not like forge prevents you from using vanilla systems or writing your own.
@@Speigerwait people are using asm in Minecraft mods now? :O can you use c/c++ instead of java?
Alternative and competitor are the same word
For anyone wondering about the Quilt situation, and why it split off: the creators had political and social clashes with the Fabric creators. Accusations were made from Quilt devs to Fabric devs. I looked at the evidence they provided, and I didn't find the evidence sufficient in the claims. But, to sum it up, they split because the devs didn't like each other.
sounds like poly mc and prism.
except the prism devs attempted a hostile takeover before getting kicked off and then slandered the lead dev afterwards.
The reason plugins are more compatible with all forks of the software it was designed for is basically a design thing, it's the same reason why a plugin that was made 10 years ago may still work even right now on any software, in fact that's the reason plugins were even invented, Also developing mod loaders and mods in general is more complex and requires a lot more effort than plugins and their softwares
Ofc! But i was more refering to the server software themselves. For example Gale has some serious rewrites in it but plugins still function.
And, Spigot is a fork of Bukkit, which Bukkit was made by Dinnerbone, who now works for Mojang. If Mojang allows it, then Bukkit (or parts of it) could be merged in Minecraft.
@@samuelhulme8347 im sure some of the protocol and handshaking has made its way into modern Minecraft, but i doubt it
@@Cygnus_MC People complained that Forge is bloated and hurts performance so devs started to make their own mod loaders. I heard no one complaining about how Bukkit or Spigot is bloated because they work well. So devs like them and don't want to use something else, just something better for their needs. This is why the server devs forked each other and mod loader devs made new projects. As a dev I'm honestly surprised how plugins work with this many servers. Because when it comes to software development it's rare to see single standard. There are many Minecraft launchers, there are many social media platforms, there are many apps which do the same thing... I 100% agree that this can be frustrating for the users, but this is how the world works. And it's the same with the Minecraft servers once we look beyond Spigot forks. For example I don't like how I can't join from Java edition to a Microsoft hosted Bedrock world (not realm, just a world a friend is currently playing on). But that's a different topic.
Dude have you seen the Linux world... Forks here, distros there
At the moment for me it's always a question of "do I want to make my next modpack performance-oriented or content-oriented and which mods do I need to sacrifice for each?"
it really depends on which version, if you are trying to make a vanilla plus pack then go with 1.16+ packs, im not sure on which modloader though never used anything other than forge, but in 1.12.2 forge you can add good content and have it optimised well
@@radactivi Thing is, 1.19 Fabric is much more optimized than even Vanilla 1.8, which in my opinion is the most optimized Vanilla version of the whole game. Even if you have a 100+ Mods 1.19 Fabric Modpack, it's still probably more optimized than pure Vanilla 1.19 (with 1.12 being about the same level of optimization I think). The problem here is that _Forge 1.19_ has way more mods that I like, but many Fabric mods are exclusive to Fabric so I end up having to choose between Fabric or Forge on even terms.
@@mifiwi3438 Oh i see, well its probaby annoying now that the modloaders have been split, but it was bound to happen
I would like to name drop two mods I've been using that alleviate a little bit of this messy issue. Forgified Fabric and Sinytra Connector. Forgified Fabric is basically a Forge port of the FabricAPI which almost every Fabric mod uses, and Sinytra Connector is a compatibility mod that works alongside Forgified Fabric to port the usage of third party API's over from Fabric to Forge. Using them both together, they allow many Fabric mods to work perfectly on Forge with little to no issues. Currently, the mods only work on 1.20.1 and not every Fabric mod can work on Forge through the connector. Some mods Do work, but still have conflict with the internal code for other installed mods, like Soulslike Weaponry and L_Ender's Cataclysm. I also do generally prefer Fabric over Forge not just for its improved performance, but also its more simplified crash screens that ACTUALLY tell me what crashed, but unfortunately, there is no Fabricated Forge to port Forge mods over to Fabric. Yet.
But these mods have been incredibly useful in making modpacks as they create a small bridge for Forge and Fabric to cross that we have been searching for so long.
Here are the mods:
legacy.curseforge.com/minecraft/mc-mods/forgified-fabric-api
www.curseforge.com/minecraft/mc-mods/sinytra-connector
The Forge vs Fabric discussion is similar to the "Windows vs Linux" fight, where one is called old and clunky (forge) but with an established portfolio of software (Big mods only available on forge) vs Fabric/Quilk/NeoForge, that is called as a better version for being more stable, and having cleaner code, but being problematic by the mob/collective mentality that they share, often crippling themselves while trying to cripple others
It's more like X11 vs Wayland
To me it's some key mods that make me choose fabric (sodium indium and distant horizons)
@@peksn literally the only mods that I use on fabric
Even though they are the most vanilla things, they are in my opinion the ones that make me look forward to minecraft the most, it's just so pretty, if mojang wanted they could do a Minecraft 2 just by putting shaders and LOD of a few kilometers and that would already be a huge foundation @@elecman748
@@peksnDH runs on forge too fyi :)
I typically use Forge because it's what I am familiar with and has all the same mods my friends and I enjoy. But I won't lie.. It's slightly frustrating seeing some cool mods on the other modloaders that I want play with but can't. I wish that I could.
I understand you well my friend, i have your same frustration. Me and my friends started on forge but recently changed to fabric cause one friend could not play without BSL shaders (iris and sodium dependent now...). I on the other end really miss some forge mods, like iron's spellbook and gravestone mod. All this mess with mod loaders, compatibility and shit is really frustrating for people that simply want to have some fun 1-2 hours a week
BSL shaders do run on Iris+Oculus on Forge, we use them in our heavily modded server along with Rubidium, Canary and a shitton of other performance mods. Hope this helps!
@@buguiui7514 Really? I didn't know about oculus. Thanks a lot for the suggestions. What other performance mods you use?
BSL still works on optifine, I’m using the latest version on a forge 1.12.2 server that I play with a few friends
Some functionally isn’t there with certain mods but BSL is “supports” all versions to 1.7.10
I personally prefer Fabric, but I use Forge, Fabric, and Quilt based on the mods I want. I have never heard of other loaders, I started modding on 1.16.5, and I know about Quilt because I saw it on RUclips, and its on the PrisimLauncher modloader(list of available loaders for mods) list.
Modloader is old. Rift died instantly. Neoforge is forge but without lex (so better uograde) neoforge is also planning on working off some of that technical debt
neoforge and quilt are go-to for me. I can't pick one, because on each side there are a lot of mods that are too good
As a consumer of mods, the fact it isn't just 1 modloader, really irritates me, I want to mix and match mods and it's harder since fabric and the others came
I don't care what modloader it is but I just want there to be 1
I use forge for older versions and fabric for newer
@@mythbunkers4716 I just prefer to be able to play the latest version modded
@@mythbunkers4716This strategy makes the most sense to me
Another point to think of when comparing the plugin ecosystem and the more general modding system is, that plugins are only written for the server side of the game, which doesn't have to deal with anything graphical and direct user interaction. Since general modloaders have to deal with both sides (client and/or server), the complexity is way higher and more breakage between updates happens.
Yes that is understandable, but there are server sides mods that still have to content with no compat between loaders
"There is no reason to complain!"
Be me, enjoyer of mods, find a mod that I like, realize its for another modloader, which is incompatible with all my other mods.
Stubborn mod creators don't want to make mods for different modloaders or older versions of the game.
Stubborn community outright causing mutinies left and right and involving petty things like politics into the mix.
no reason to complain, no reason to be mad at all, nuh uh, not a single reason.
the minecraft community is very mature
This
Last point is straight addressed to quilt i suppose
TSMT
I hope neofroged's efforts to rewrite a major portion of the loader in modern versions go well, and it becomes a competitor both to forge with capabilities for large mods and to fabric in terms of performance. Although I do think the competing standards xkcd does apply, there's a side problem where each loader has a different focus, so one loader (neofroged) that is able to finally satisy multiple goals would finally provide a more objectively good platform moving forward and hopefully become the default rather than having to seemingly decide between performance and capability (or whatever it is that draws large mods to forge) as it is now.
So I use a tool called Multiloader. Neofprge has actually been working with the devs to make a "unified project" that included forge Arabic and neoforge.
I think long term there is a move to make all code work on each loader with highly technical mods having loadper specific projects.
that moment when i see a bunch of mods that perfectly complement each other to make the perfect modpack only to look at the loader section and have my hope crushed . . .
this I don't understand. If you find a cohesive modpack, what is stopping you from playing it? The only issue I personally have with the differing modloaders is that half the mods I want to add to the modpack are forge and half are fabric. But if you already *have the modpack*m then what is stopping you? In my personal experience, the issues only exist when creating a modpack.
"when i see a bunch of mods"
Love your content was always something that I wanted to do myseld but never actually did because of not knowing as much as I should to make content of it.
Great Video!
Thanks for the support!
Glad we in Better than Adventure community have only one mod loader, no such problems as you have. Also it called Babric so extra points for funny name :D
I need to check that out
@@Cygnus_MCwhere do I go to learn about that, and how noob friendly is the design?
I'm not ashamed to admit I'm dependent on in-game wikies and jei to the point I just can't use complex mods that lack them.
There are so many more mod loaders, but almost all of them are dead or for legacy versions. Someone even tried to create universal api on top of all of them, but seems to have abandoned this idea (loader complex)
A universal loader just ends up being another loader. See XKCD 927.
It would be nice if Mojang developed their own modloader with a complete API and tools to give a standardized modloading platform. Alas, Mojang can't even be bothered to optimize the java experience.
Do datapacks ring a bell?
@@Cygnus_MC No not really. Datapacks do some things but they aren't comprehensive enough for developers working on bigger projects. Datapacks were intended for the creation of minigames.
@@Cygnus_MCDatapacks are more meant for altering existing code IDs, not adding new ones much less adding completely new functions like the weather and physics mods.
@@Cygnus_MC Datapacks lack too many things - there was a person that has done many impressive things with datapacks, but for their most recent project they said that couldn't... *Checks notes* Add new inoffensive decorative blocks... So they had to do their newest project in a modloader. Datapacks also have the limitation of being only able to code in minecraft commands, which aren't exactly intuitive. SethBling managed to make a realistic rigidbody physics engine using a datapack, but he had to do it using a programming language, that he himself created, that simply translates itself to a datapack. How he managed to create an _efficient_ code-to-minecraft-commands transpiler is beyond me honestly. Even then you can see that most of the inner workings of his physics engine is based on scoreboards... Which are... For the lack of a better word... Disgusting to use.
Absolutely NOTHING can replace creating a modding API. Nothing. Nada. When you try you end up essentially creating a separate programming language just for your game. At that point just implement a goddamn API.
Videos like these make me glad I never play modded Minecraft past 1.12.2
personally i liked fabric a lot so when i tried Quilt it felt just like home and atm i am fully onto it
.
Fabric became mainstream at around 1.17. Forge was nowhere to be found and everybody was waiting and waiting for them to update their loader. Right then and there, Fabric took over. 😊
Yeah, I switched to fabric for a similar reason: I was amazed at how quickly all the mods updated
Waiting for all the mods I use to update for a new major version went from taking a month to taking a week
I doubt 1.17 microupdate had any serious impact on loaders when 1.18 was released shortly after. It was the issue of 1.12 days when Forge took time to "fix" and "rewrite" issues bts that were causing losses in performance in stability. It took so long, that 1.13 didnt have modded support for long enough for Fabric to be made and grow steadily from there on due to all other factors alr mentioned on the vid
It's a messy topic for me, as someone who makes modpacks for his friends. I personally prefer Fabric, it just seems cleaner and easier, but for my big modpack, I'm forced to use Forge because of mods like Alex's Mobs, Aether and the Twilight Forest (TF no longer is doing Fabric updates and Aether Fabric is still a WIP), amongst others.
The big issue is, there are many Fabric only mods I really want to install, which leads me to the only solution - Sinytra Connector and Connector Extras, both of which just barely work.
It really makes me wish there was one universal modloader, but alas, there's not.
Another great video!
At the moment I'm using forge 1.20.1 with connector to play an all bunch of fabric mods. Having both of them is really cool, it just need a bit of management because Modrinth doesn't download automatically the dependancies mod if you are using the wrong loader. Btw awesome video, I'm looking forward for Neo Forge evolution
Hey! connector effects a lot in the performance? if not, do you think it is already stable enough to use it?
@@darkromano_ I play minevcraft on my laptop without a GPU but with my settings I haven't seen a big difference in performance, I stay at 60-70 fps with embendium (sodium doesn't work with connector, you have to use forge ports)
Felt it when you said manually doing your own mod packs, I felt that
It's a lot more complicated than you're making it out to be, and some choices were political instead of functional.
Forge originally started to fill requirements that ML originally couldn't without a pretty big overhaul of the internals. That means the original basis of Forge is so far back that the code base is suffering tech debt. The maintenance of Forge today is likely just so that forge mods have some time to transition to a modern loader before Forge is discontinued, though that is a complete guess by me.
Fabric originally started to address the tech debt in Forge, developing under a different design philosophy to fill the problems that Forge had, as well as partially to give a platform away from Lex who, as you mentioned in your video, was a difficult person to work with. It makes sense that Fabric isn't compatible with Forge, because they simply aren't working under the same principles
Quilt was in part due to a problem with Fabric's management. They felt that Fabric could go south by having a core team, and disagreed with some of the design decisions behind Fabric that they couldn't revert, and so they built their entire fork around the idea of being community driven and working off a "patchwork" modding system, where mods connected with "yes, and" rather than "no, but". I also vaguely recall DoctorR4t talking about transphobia in the fabric community, but I don't really remember nor do I know enough about it so I'm just leaving it as a note.
With that in mind, it makes sense that Quilt doesn't really want to support Fabric mods (though they do) as they're going down a different path, and the changes are gonna get further and further apart from Fabric, which will make maintaining compatibility harder and harder.
NeoForge was, as you said, due to a change in Forge management and a requirement of breaking changes that were so destructive that they simply could not retain parity. It was necessary, not from the player's perspective, but from the developers' perspective.
At the end of the day, while modding is about the experience players get, it is almost entirely voluntary and entirely founded by the community's desire to create mods. If the tools you're using to create are bad, you won't want to create with them, and so the community doesn't get mods. This explosion of new mod loaders is necessary at this point in time. As modding becomes more advanced, almost its own game, and as vanilla code gets more and more complicated and spaghetti and low performance, it is essential that we find a long term way to mod the game that lets modders do anything without being over complicated, and the only way to do that is through trial and error.
Quilt is a completely unnecessary modloader. Its existence serves no purpose other than dividing the community.
@@Sedna1694 quilt exists partially because a member of fabric's dev team let his personal political beliefs get in the way of improving the mod loader. Don't like quilt? blame fabric.
@@ashermccready No. They didn't need to make a new api. There is no end to this. Making a new api is stupid
@@Sedna1694 Neoforged is much the same as quilt in this situation imo. From my understanding, Lex already had intentions of passing over forge to a different ownership once his house was paid off, and the split was not discussed even remotely when it happened, leaving a lot of information left in the dark.
While Neoforge are making lots of changes, so is forge. Lex is rewriting the majority of the internal loader code atm, and afaik he has plans to clean-up the tech-debt on the API too. So its very much become another useless split like Quilt.
Really, I think its silly to be using anything other than Forge or Fabric. But we will have to see what happens as of 1.21. With Mojang starting to make stuff like blocks data-driven, I think we might slowly start to see mod loaders become more useless regardless.
@@TurtyWurty same bro 👍
I dont remember when but wasnt quilt supposed to be the holy grail for modders where it would run both forge and fabric?
I don't know exactly how it is now, but before Quilt was even created, some of his developers were trying to create the mod that allowed loading of Forge mods on Fabric. Then the developers of this mod created Quilt and moved the mod to it, kind of, because at this time this mod seems to have been archived or severely slowed down in development. Oh and I remember that the developers somewhere said that work on the mod will continue after they released quilt api or quilt itself
@@izeexes oooh I see
i remember back in the days before forge. when you had to install 7 different modloaders manually to your bin folder and PRAY it didn't explode and you'd pretty much have to start from scratch.
12 year old me was elated when forge finally released and conglomerated all the mods into one loader.
Now we're back to several different mod loaders again...
IIRC, fabric also came into existence because it took forever to port Forge past what is commonly referred to as The Flattening (part of 1.13), with there being an age where 1.12 and 1.7 reigned supreme.
Great video!!!
mod dev here, over 4mil downloads. really hope that all this modloader stuff ceases; really hope i don't have to port everything not only to the correct version on one modloader, but to several. would just be a bigger pain in the ass
time to move on to fabric boy
@@snackoman1577Do you hate modding or something?
Quilt actually allows fabric mods and is in fact backwards compatible almost in its entirety. So basically half of this video can be thown into a dumpster and nothing of value would be lost
The Quilt mod loader initially supported mods from the Fabric mod loader. The Quilt mod loader, unlike Fabric, allows you to run both your own Quilt mods and Fabric mods.
P.S. But I love Fabric.
We need an update: there's Forgified Fabric API and Sinytra Connector, which are Forge mods with the goal of making Fabric mods playable on Forge, which somewhat breaks that border of parity. It'd be great to see this be for other loaders like Quilt.
Hmm I'll likely cover it however my main point is that it modloaders themselves are incompatible. While its awesome talented modmakers are fixing this issue. Its an issue modloaderdevs should keep in mind
...So I'm either about to lose Create and Thermal, or about to not be able to update my installation for another few versions until the ripples from the NEW salvos in the Modloader War™ subside, is what I'm hearing from this.
So, basically....
Fabric: Fine, I'll do it myself
Quilt: and we took that personally
NeoForged: We have Forge at home
Minecraft modloader community is one big meme
i just stick to 1.12.2 due to this confusion.
Me and my friends wanted to install some small visual mods to improve our vanilla experience, once we found out that there were a bunch of different mod loaders and that some mods were made for some of them and not for others, after watching a bunch of tutorials we just gave up and played good old vanilla minecraft. Honestly, I don't have the patience to figure out this mess that is minecraft modding just to have some visual improvements. Installing optifine and some resource packs is the most that I will do now.
Patchwork is a project which tries to create a way to run Forge (and prolly NeoForge) mods on Quilt
Patchwork is dead for long enough time as far as I'm aware (and got its repo on github archived)
When I do mods, I always require AE2, Thermal Expansion, and Tinker's Construct. Unfortunately, not all of them are on Fabric or other mod loaders as far as I'm aware, so I'm stuck with old Forge for now. Plus, they have better extensions there.
I can relate so much to these videos. Example. I play with the Minecolonies mod, and I use the Resource Pack Conquest. Minecolonies has made it clear they will only use forge, but they will not update/support older versions. Conquest Reforged has made it clear they are only working with Fabric, but they do have a forge version, but they will never update there forge version.
The main issues that upset me so much is finding something I enjoy, half only works for Forge, and the other Half only works for Fabric. I am called Entitled all the time, even though I am very new to Minecraft, and only recently have I found out some mods conflict with other mods, and its not a simple click download, and play. I use Curse Forge, when I first started playing Minecraft I made my own mod pack, and could not get it to run for weeks because I didn't know about mods conflicting with others. I just thought it was click download and play.
This is what new players run into the first time they play after watching a Minecraft video they enjoyed watching, and I HATE when people reply back Don't use Optfine, Use Sodium when they know dam well Sodium is mainly used on Fabric, even though there are fork versions for Forge. Its just a very BIG MESS, and the Authors know this they just don't want to take on the headache some of them created for them selfs, and put the blame on players.
man i just want all the mods i want to download to work on my minecraft. having to jump through compatibility hoops and choose one modloader over others at the cost of choosing between sets of mods is absolute crap.
the modding user experience is atrociously painful because of all this stupid infighting between modloader developers. I await the day for when we finally get ONE modloader for ALL mods, its not impossible, its done in literally every other moddable game, Minecraft is the only outlier here and its ridiculous. i could care less if one has 5% better performance than the other or whatever, im so sick and tired of having to pick and choose the mods i want depending on the loader they were made for.
If forge devs just abandoned forge seeing there was A BETTER MOD LOADER in the horizon or did something simillar everything would be so great...
but instead they kept on pushing it until neoforge became a thing, just out of pettiness i think.
it is like if you were selling old ass software, but instead of cathing up to the new ones, you just keep seeling old crap with little effort to improve it.
as a modpack creator, the nightmare of having "fabric only" "forge only" "quilt only" mods is unfathomable.
4:31
I think this small correction should have been a bit more than a small correction imo
quilt has supported fabric mods for a very long time now, and that kind of invalidates a lot of points in this video
i see quilt as how Prismlauncher was to PolyMC, same with neoforged.
i don't see how quilt's situation is any different from neoforged lol
I personally think the fact they started out as not allowing them still kinda bolsters my point. Like i said reading into the code, quilt is most certainly doing stuff, but the stuff isnt worth the extra confusion for end users
@@Cygnus_MC yea i suppose thats fair 👍
Yes, this is something that also bugged me when I was creating a modpack for my friends a month ago.
Forge is a modloader that runs poorly, mainly when you have many mods. We are having like 250 mods and I also want to play the game, but with a pc that has like 7yo components, it doesn't run good at all.
Fabric is my preferred choice of a modloader, It is fast, responsive and everything works quite nicely even with many mods. It also has quite a lot of mods already so you can build modpacks with it.
Quilt is quite a weird thing. As it is a fork of fabric, I expected to be able to run fabric mods on it and quilt mods on fabric. But it only works in one way, not the other, which makes me kinda sad.
Neoforged is.. dunno. haven't tried it cause there are no mods for it really in comparison to the big ones.
multiple mod loaders just makes it harder for the players, you can't mix and match mods because you can only use mods for that specific loader unless the developers makes a version for the other versions. it sucks because there are so many awsome mods but you cant use them because one is for fabric and the other is for forge and the other is for quilt.
we either need a compatibility mod that allows the other loaders mods to work on one loader or we need to nuke the other loaders and go back to a single modloader
welp that quilt incompatibility part after your correction was funny
Oop
i use both forge and fabric depending on what im doing, for my casual play and custom modpacks, fabric, for a lot of the big professionally made modpacks, forge
I use Fabric for newer Minecraft versions and Forge for older ones that don't have Sodium. On Beta/really old versions I just play Vanilla.
honestly, there are too many mod loaders, because they all end up being incompatible with each other
fabric/quilt are inferior to literally every other modloader, because you need so many different "packages" and extra mods that just end up making the experience just exactly the same in the end
fabric/quilt only really works well with smaller and smaller packs, where theres more that each individual mod can then do
if anything, something like NeoForge would be the better loader of all, because its still forge, but its getting its knots untangled and its methods optimized, and in the exact same way that fabric was doing it, in such a way that fabric is now redundant to forge (now neoforge)
Though some modders tout inclusivity as a motive to create their mods for a specific loader, but they have also excluded their players. Sure, the modder doesn't have to care and can do whatever but they have abandoned the players they were catering to.
Quilt also was pretty much always compatible with most Fabric mods also, they just don’t promise complete backward compatibility with it.
I still remember the days when it was all either Forge or ModLoader and while most good mods ran off of Forge, a select few really cool ones were ModLoader only.
Good times.
As a developer i must say: as client side we just need a standard interfaces which will not change or change really rarely at all. Which will have unified events and unified type. Then it's up to loader on how to load things.
But Minecraft changes internally in every version
@@thewhitefalcon8539 That's Mojang's fault for not releasing Diff Against documentation for the code changes.
It's not that Quilt recently started supporting mods from fabric. Ever since it split off it has supported fabric mods (however support isn't guaranteed for the future). The only caviat is, that Quilt mods don't work on Fabric.
40k reference in MY minecraft mod video essay? yes please
Vintage story is a great game like mc but alot more work to get where you want to be in game.. its more for adults and modding is built straight into the game
Oh boy you're gonna love the video i did on vintage story:)
Depends soley on the mods I'm running, although I have a few resourcepacks I really like that only work on optiforge, even with all the CIT substitutions using Sodium-Forge/Fabric.
so many mod loaders legit slipt the modding scene too much there is often where there is a forge only mod i want in my fabric modpack or visa versa
its already bad enough with the minecraft versions some mods just stop at 1 version of Minecraft but now even more slippting please no more mod loaders
at this point we need a form of API where mods can just work between the loaders it is really annoying for users now since all modders didnt move to just 1 loader and this slipt exist
i dont care about what loader is better i am complaining about the slipt itself that slipt is honestly 1 of the worst thing to happen for mod users and properly also mod dev.
i remember in 1.7.10 mods was insane compatible with each other to the point pipe/cables covers used forge micro blocks so you didnt need covers for each pipe mod
but now there is non covers for those mods or covers of each texture in the game for each mods that add cable/pipe covers and that cant be good for lag
and other small QoL stuff between mods just complety lost like this
Modrinth makes testing packs/loaders/mods/mc vers pretty easy; way easier than 12 yr ago when I was first modding mc.
The difference between a mod and a plugin is that the mod will make some changes for the client side, maybe UI, new entities, blocks, items, etc. While plugins are specifically for server side. While you could drop in a resource pack and/or a data pack to give the impression of new content, plugins just reuse the same existing items to achieve the same result. These are considered workarounds and require a bit more creativity.
Okay so im new to all this mod thing, witch one is the best and secure launcher? And cracked (cuz i dont have a minecraft account) i have used technic launcher in the past but it no longer works for cracked
Imagine if Mojang released an open source modding API that anyone could contribute to and help improve... nahh couldn't be them.
I actually have a video about that! If ur interested in my take
They did. It's called data packs and it really made the core game code a thousand times more complex. Pray they don't try it again.
@@thewhitefalcon8539 data packs are way too limited.
@@thewhitefalcon8539yet thousand times easier to mod!
I personally use Quilt since it became kinda known. It worked with all needed fabric mods from the get go and quilt has some really cool small enhancing mods, so I went with it. (I only play vanilla with clientside mods)
Pebble our lord and saviour
I honestly didn't even know there was anything but forge and fabric
my prediction is that fabric & neo forged will be the most popular in 5 years, with the other two fading into obscurity.
love the Warhammer reference
i honestly find it annoying when theres two mods i enjoy but can't use at the same to because there not compatible
Ive played a bunch of modpacks, and ive to say from my pov
Forge Modpacks just worked out better in the end than any Fabric Modpacks.
Theres a big amount of politics and drama that doesnt have to be in modloaders for a block game or lots of things in general...
When i saw there's yet another modloader popping out i honestly felt like facepalming, but... Hopefully it will be last time that new modloader pops out. As an user i have incredibly hard time to choose which version and let alone modloader to play with.. I have like probably 100 different servers because of this, different mods and different versions and modloaders because i solely can't decide where i want to play in. Now, it might take awhile (not sure how much different it is codewise, but anyway), but hopefully neoforge will be the one ongoing now on for longest of time and becoming the main one for latest minecraft... If only other modloader devs can unify with neoforge and drop other ones, maybe we can all play all new incoming mods in one without worrying about different modloaders... I have zero experience in coding, so im fully user based commenter and thought to share some of my own thoughts.
fortunately as a user (though I do know a little Java and tried my hand at the modding thing off and on), modern multi-instance launchers make this much less aggravating. I can have both a fabric and forge mod install going on at any given time depending on what mood I'm in.
or I can fiddle with a load oarder and then never actually play it, like I do Skyrim heh.
8:20
forge is used for older versions [like 1.12 prior generally] (since it's more compatible/optimized with older mods)
fabric is used for newer versions. that's at least how I view/use it alongside the people around me.
I'm glad for things Forgified Fabric API & Sinytra Connector Mod.
Can you answer me if curseforge is sate again? I was wondering in downloading roguelike and dawncraft. Also, can you help me? In curse forge modpacks, my game keeps having massive stuttering, but i have good specs, an Ryzen 7 7800x3d and an Radeon rx 7700 xt, only 16gb of ram too.
This is the chaos we feared, no one wanted a Risugami ModLoader vs Forge again, and now it has only gotten worse.
I just stick to Forge because it's what I'm used to, but seeing now that some mods might not work together is a disgrace.
Has the birth of any of these modloaders done more good than the compatibility issue they created?
This is exactly the point most people are missing here. I still remember the ModLoader vs. Forge times, and I was so happy that it was over. Now, seemingly, every other Schmuck wants to create forks of ModLoaders for no reason.
This really will be the death of modding. And if not that, a second dark age.
That 40k refrence was awesome.
me out here crying as i have all these different installed instances due to forge and fabric alone. i haven't even tried quilt or neoforge yet due to this LOL
Fabric literally runs laps around forge in terms of performance, and since I always to try to max my MC having all the perf mods is a world of difference. Let’s not forget the load times of large mod packs not even being comparable between the two.
I only really see fabric being the main loader moving forward because of its stability and current support.
pebble
After seeing the mess in the Forge sever before the takeover, I'm so glad that NeoForge exists, a good refresh and a lot of stress taken off after kicking that abrasive person
I was installing Forge mods manually for years with very few problems and I was completely open to trying out other loaders. I tried with Fabric and didn't have the same experience so I started using the Curseforge app and was able to get a decent sized modpack to run. It wasn't long though, after updating a few Fabric mods through the CF app that the modpack wouldn't open anymore so I went back to using Forge. I tried several times to build a Fabric profile to no avail. I am still using Forge both manually and with the CF app and have even started using the Modrinth app and NeoForge with almost no problems but I've given up on Fabric for now.
I had similar issues with Fabric on CurseForge, but on Modrinth it works great. Modrinth is pretty much just better than CurseForge in general.
I have a fabric mod pack with 498 mods that works beautifully with modrinth. You should try the modrinth launcher, it makes making mod packs with fabric sooo much better