Incompatibility with Yarn mappings when used as dependency

[DiamonDoughnut]

Mod Loader

Fabric

Minecraft Version

1.20.1

Botania version

1.20.1-445 & 1.20.1-446

Modloader version

Fabric: Loader 0.16.0

Modpack info

No response

The latest.log file

https://pastebin.com/U7UYgXHe

Issue description

In IntelliJ Idea dev environment with no code other than gradle and fabric.json modified - Main and MainClient classes are empty - as well as in written mods with one to multiple dependencies, Mod will compile without issue, but crashes on "runClient" configuration with the above error - I believe this is due to the botania.refmap.json calling to the classes and methods in original minecraft mappings, rather than yarn mappings - though I'm not too experienced with mixins, so I'm not certain that's even an issue. Xplat uses base mappings and conflicts with any attempt to use Yarn mappings to call directly to any item/block in Botania, so not having found a way to circumvent this, I would like to look into either helping push towards a fix or to be informed of an effective workaround.

Steps to reproduce

1. Create new mod in IntelliJ dev environment
2. Enter Botania Fabric version in dependencies and proper maven repo into mavens
3. (optionally) genSources with cfr or vineflower
4. run configuration runClient
5. Error after short compilation and attempted client start

Other information

No response

[TheRealWormbo]

I can see a similar issue with Botania itself and its Trinkets dependency when upping the Trinkets version to 3.7.2 – code compiles fine, but datagen or trying to run the client crashes with a mixin error. (Trinkets seems to use Yarn instead of Mojmap as well.)