Hi, I know this does not cause any issues, but solving warnings is always good.

@Mixin target net.fabricmc.fabric.api.client.screen.v1.ScreenEvents is public in seamless_loading_screen.mixins.json:mod_compat.fapi_0_30_0.ScreenEventsMixin and should be specified in value

Maybe you can solve this? I don't know much about Mixin but you probably need to add @Public or something together with @Mixin.

there's actually 2, the other one being:

@Mixin target me.juancarloscp52.bedrockify.client.features.loadingScreens.LoadingScreenWidget is public in seamless_loading_screen.mixins.json:mod_compat.bedrockify.LoadingScreenWidgetMixin and should be specified in value

This warning appears because I use target="class.path" instead of value=ClassName.class for these two mixins. I did this so I didn't need to have the two mods (Bedrockify, and Fabric API 0.30 or above), because Bedrockify changes a lot of screens, and I need to test the mod without it, and fapi 0.30 was causing some problems, so I was consistently switching fapi versions while trying to fix it.

Since fapi 0.30 has been out for awhile now, I probably don't need to worry about switching between pre 0.30 and post; and thanks @Pseudo (which I just learned about) the class doesn't need to exist at compile/run-time, meaning that I can switch to value= without requiring people to use fapi 0.30 or higher.

However, for the bedrockify one, I will not be changing it, as it would make testing more complicated, and prone to error

A commit has been pushed that changes fapi's mixin