Switch to fabric-api ID for Fabric API

[Poopooracoocoo]

https://github.com/MinecraftFreecam/Freecam/blob/main/fabric/src/main/resources/fabric.mod.json#L32
https://github.com/MinecraftFreecam/Freecam/blob/stonecutter/fabric/src/main/resources/fabric.mod.json#L32
https://github.com/MinecraftFreecam/Freecam/blob/beta/1.21.11/metadata/src/fabric/fabric.mod.json#L32

Easy fix, prevents user confusion. The fabric-api ID is used on Minecraft 1.18.2 and above. You don't seem to support older Minecraft versions.

[MattSturgeon]

Thanks for the heads up. I've addressed this on the stonecutter branch: 267e0e1

[Poopooracoocoo]

I want to clarify that the fabric-api ID is used on 1.18.2 too. It's not used on 1.19 and 1.19.1, but the only people I've ever seen use those two versions are those who don't know better.

[MattSturgeon]

Because fabric-api also has a provides: fabric alias until 26.1, I don't think it's too critical to have it exact.

Did all fabric-api builds of 1.18.2 use fabric-api? It sounds like they may have switched sometime during the 1.19.2 cycle and then backported the new mod ID in later 1.18.2 hotfix releases?

I'd like to avoid Freecam 1.18.2 builds complaining "needs fabric-api" when the user has an older (but compatible) fabric mod installed, assuming that's a valid scenario.

[MattSturgeon]

Freecam itself only actually uses two fabric-api modules. So I may change fabric.mods.json to require those, instead of the entire thing. The downside being that error messages will be less readable.

Or alternatively we could jar-in-jar the two modules and drop the dependency entirely. This makes Freecam easier to install, at the cost of an extra 95kB jar size (1.1MB vs 1.2MB).

I'm leaning towards the second option.

[MattSturgeon]

I'm leaning towards the second option.

At least as long as Freecam uses Cloth Config, we will transitively depend on the entire fabric-api. So there's no point in bundling the modules that Freecam itself uses.

[Poopooracoocoo]

Did all fabric-api builds of 1.18.2 use fabric-api? It sounds like they may have switched sometime during the 1.19.2 cycle and then backported the new mod ID in later 1.18.2 hotfix releases?

Yeah that's right. Not all releases for 1.18.2 have the new ID.

It's fine to leave it as is