Fabric API is the core library for the most common hooks and intercompatibility measures utilized by mods using the Fabric toolchain
This is SEPARATE from the Fabric loader! You need both for most mods!
Keep in mind the project is in early development and requires the Fabric mod loader!
is 1.12.2 out
In reply to MinnyMeLeeds:
Fabric is for 1.14+, not for 1.12. There is not and will not be a 1.12 version.
In reply to MinnyMeLeeds:
Liteloader is for 1.12.2 and prior, Rift is for 1.13/1.13.2 and Fabric is for 1.14+. That's pretty much what your looking for (Liteloader). Look for Liteloader mods and you'll find some that support Fabric now do support Liteloader (Autofish, Voxel, etc. for example), but most new Fabric mods don't support Liteloader or Rift as they are strictly for Fabric. That and Fabric isn't ever going to 1.12.2, Fabric is a 1.14+ mod scene thing.
this works for 1.14.2?
In reply to Chelise105:
yes
Well I installed the files and double then triple checked I had the right versions (1.14.2 non-snapshot, etc). The game loads fine. My mods load and function fine. But often the interface will lag slightly when selecting or moving items in the three slots in the top-right portion of the inventory.
Every other slot is fine. And it's just the interface part. Mobs and whatnot still move just fine in the background, and the debug screen still says I'm getting 80+ FPS.
This only happens when I have a mod enabled, which I only have two anyway (Auto-Fish and Voxel Map)
Playable, just slightly annoying - and I have no idea what's causing it or what to do about it.
Complete instructions for complete noobs to install Fabric on Windows.
Tested and working as of June 18, 2019.
1. Download both parts of Fabric (the API and the Loader). The API is on this site (top-right link). The loader (with instructions) is here: https://fabricmc.net/wiki/install
2. Run/execute/double-click the Fabric Loader installer file ("fabric-installer-....jar/exe"). This will create a new profile in your Minecraft Launcher.
3. Put the Fabric API jar file ("fabric-api-....jar") inside the "%APP_DATA%/.minecraft/mods" folder, but not inside a version numbered folder.
Put any mods' jar files in the same folder as step 3. For me, I started using Fabric for the VoxelMap mod. https://minecraft.curseforge.com/projects/voxelmap
I hope this is helpful! :)
Will there be a 1.14.3 Pre-release 3 version coming soon?
Would this be able to coexist with forge and not crash? (if i have 1.12.2 mods in the same place as 1.14 mods will fabric ignore the 1.12 mods or will it crash)
Please help,
[16:01:32] [main/INFO]: Loading for game Minecraft 1.14.2
[16:01:35] [ForkJoinPool-1-worker-5/WARN]: Mod ID fabric uses outdated schema version: 0 < 1
Failed to start Minecraft:
I'm using Fabric API 0.3.0 build 176
hello, why does the fabric work in snapshots of 1.14 and 1.14.2 and does it not work in the final releases?
In reply to gabistar18:
It absolutely works in final releases as well, though?
In reply to asiekierka:
Yes, it works . I had problem to use the fabric and fabric api along with the mods that needed it, but I solved the problem by watching a video XD
In reply to gabistar18:
Which is??
Does the latest build work with 1.14.2, or the snapshots? The file name and the game version are directly contradicting each other.
In reply to mariovsluigi666:
1.14.2 and 1.14.2 snapshots; not 1.14.3 snapshots. CurseForge isn't granular enough.
What is this, and what does it do. I am new to all this mod installing lingo and what everything means. Please answer soon and thanks in advance.
In reply to N1TR0S1TY:
So there's the base game (Minecraft) and then there's modifications to the base game (mods). In order to make the mod work, you usually need to add a mod loader (Forge/Rift/Liteloader/Fabric) to the base game. Sometimes the mods and mod loader need an extra file to communicate with each other correctly. these are usually called APIs, but I honestly don't know what that stands for.
You could say that the game is the frame of a car, the mod loaders are the engine/transmission/etc, and the mods are all of your personal customizations. And sometimes you need some nuts and bolts (APIs) to hold it togther. Not a perfect metaphor, but hopefully a useful one.
In reply to XanderJayNix:
Application Programming Interface
In reply to N1TR0S1TY:
In reply to swordkorn:
Correct. An API is like a barrier that programs can communicate via.
An example of the functionality of APIs is in the form of a letterbox.
Yeah, that sounds a bit wacky, but let me explain.
So, you've got a Postman [P1], you've got You [P2], and you've got your Post [payload]
[P1] needs to get the [payload] to [P2]. He can't just open the door to your house in order to give [P2] the [payload] (a program can't write data into another program's memory).
Here's where the Letterbox [API] comes in.
Rather than [P1] crossing the boundaries into [P2]'s address (pun intended), [P1] can pass the [payload] to the [API]. The [API] then handles the transfer to [P2]. This prevents [P1] from passing unintended stuff to [P2].
Imagine if [P1] left his keys there by accident. Imagine if a program wanted to communicate with another program but the data that was passed needed to be sanitised beforehand and the first program didn't know about that (look up SQL Injection and Cross Site Scripting as examples).
Thanks for attending my TED Talk