Player

The regex partially verifies the package name, it should be as follows: ``` base package name: net.fabricmc.fabric + api/implementation/mixin subpackage: api/impl/mixin + client/dedicated server/common env subpackage: client/server/ + module name...

I'm not a huge fan of the normal prefix - it's only the color being "normal", but not the structure/naturalness. Uncolored or so might be better. The slabs and stairs...

Right, I missed that, so only the proper prefix choice question remains.

More precisely MC doesn't appear to use any Java 16 feature yet, it looks like Java 8 code built with Javac 16. So the breakage is yet to come ;)

The vanilla launcher normally replaces the jar file at this location with a copy of the vanilla client jar (with Loader's name, but still vanilla mc client jar). This for...

I don't think that's a particularly practical example, encouraging clientserver differences sounds like trouble in general. It'd be fairly easy for me to support even arbitrarily combined dependency expressions (`modA:*...

The new server installation method already buries the vanilla server jar a couple folders away, which should make this a rather unlikely

PR 680 is not meant for this use case, I don't think it'll help you with it. There are other ways like -Dfabric.addMods to go beyond the mods directory. It...

The currently officially supported way for this is limited to `-Dfabric.addMods=mods/` (or `-Dfabric.addMods=mods` to include all subdirs)

No, 680 is really only useful for code that runs before Fabric Loader, e.g. in-process launchers or wrappers. It doesn't pull in anything extra, but prevents the referenced libraries to...