Dexrn/FabricAPIStub
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A stub mod that reuses Fabric API's legacy fabric mod ID
1 commit 1 branch 0 tags 29 KiB
  • Java 59.7%
  • Kotlin 40.3%
Find a file
Exact
Dexrn ZacAttack 1df2737338 chore: init
2026-05-02 23:29:06 -07:00
buildSrc chore: init 2026-05-02 23:29:06 -07:00
gradle/wrapper chore: init 2026-05-02 23:29:06 -07:00
src/main chore: init 2026-05-02 23:29:06 -07:00
.gitignore chore: init 2026-05-02 23:29:06 -07:00
build.gradle.kts chore: init 2026-05-02 23:29:06 -07:00
gradle.properties chore: init 2026-05-02 23:29:06 -07:00
LICENSE chore: init 2026-05-02 23:29:06 -07:00
README.md chore: init 2026-05-02 23:29:06 -07:00
settings.gradle.kts chore: init 2026-05-02 23:29:06 -07:00

README.md

Fabric API Stub

A stub mod that reuses the legacy fabric mod ID, which was recently dropped by Fabric API after the release of Minecraft 26.1.

This mod provides no extra features, hell, it doesn't even have any Mixins.

Why?

It's possible that some mods may depend on the legacy fabric mod ID, causing the Fabric Loader to throw an error due to a missing dependency.

Some mods may also "recommend" both fabric-api and fabric, causing an odd warning on launch.

Will this fix a pre-26.1 Fabric mod?

It's very likely that it won't, due to Minecraft now being deobfuscated, which breaks due to older mods being remapped to Intermediary.

I'm a mod developer, how do I know if a user has the API stub installed?

Check for the presence of class me.dexrn.fabricapistub.FabricApiStub

WARNING

It is not recommended you use this mod unless it's for a very specific and well known reason.

Such reasons CAN include:

  • Mod developer forgot to change the fabric-api mod id in their dependencies before publishing their mod for 26.1+
  • You have a multiversion mod installed, which recommends/depends on both fabric-api and fabric