Player

Not sure, it's really just a simple way to expose the data from the mod jsons. Implementing toString has some benefits in the debugger, but uses that depend on equals/hashCode...

Please note that we implement a bit of a super set, allowing more flexibility around the number of version core elements and other bits like numbers with leading zeroes.

Yes it is technically correct even if not the most human readable. The declaration in mod a effectively creates 2 open intervals with 2.0.0 missing, which is what loader requests...

It needs hierarchy aware mapping-io to be fixed properly, I'm working on that. I believe the issue is that intermediary doesn't have mappings for ``, which in itself wouldn't be...

It is difficult to get them right, so IMO it is a reasonable API addition. It should also handle initializing/adjusting the state to the specific use like setting the fake...

The biggest issue I see there is moving half of loader into api territory if we're not careful..

I wouldn't bother with workarounds, a proper solution is not too far off at this point.

It likely doesn't supply a MC jar at all or an empty one, running gradle with --refresh-dependencies may help.

Recursive loading is currently only available with some customization, e.g. `-Dfabric.addMods=mods` effectively makes the whole folder recursively available

I eventually want it to initialize only the headers and lazy init the actual mappings - this may require mapping-io though, which has a few other challenges..