Player

Can you elaborate on the benefits? Any measurements?

Log4J or another lib won't happen since I want to avoid introducing deps that may conflict. I'see see about exposing it via other means though. Loader has a similar issue.

For `` there's no virtual method dispatch, but chaining, thus I'd only want to do this if some special option is enabled (optimistically assume identical constructor signatures take the same...

Tiny remapper's name generation should remain independent of MC, so hardcoding rules for its typical classes is out - only important Java ones may receive some. The same applies to...

I like the idea of adding the default variable name, not sure how it'd interact with enigma / manual mapping authoring though. Some external tool with the knowledge+analysis capabilities of...

This is a major pain to handle because it breaks in the verifier, not in the fundamental access rules. JVMS 4.10.1.8 demands " Otherwise, use of a member of an...

I don't think I can fix this properly while maintaining performance, normally the decompiler should detect the clash and rename further. It may be more practical to do extensive analysis...

It is tbd whether this should be changed in tiny-remapper. Right now it assumes none of the inputs were opened elsewhere and cleans up after itself. The global state of...

Yes it's most certainly a (known) issue in Loom (Fabric's gradle plugin), it doesn't reliably close files and is being reworked.

We can actively handle duplicates though, potentially prompting the user for whether it should replace the existing entry or add a new one (`Fabric 1.15.2 #2`, `Fabric 1.15.2 #3`, ...)