Mumfrey

As you correctly surmised I think this is the way it is because the target when designing the AP was Forge, where class names are the same between dev/prod. It...

At the moment that's not possible. Ctor invokers are a step towards removing access transformers but still aren't all the way there, *Shadow Classes* will address that and are roadmapped...

The main issue is that accessors and invokers use the method signature as part of the query, they don't support it in the annotation. Where an injector has its targets...

This honestly shouldn't be too hard to accomodate since all the scaffolding required to achieve it is basically already in place. I'll look into this.

Yeah obviously this is the reason the AP exists in the dev -> obf direction of travel, but there is no equivalent in the opposite direction. The mixin AP could...

Sorry for slow reply, I've been away at an event. Ah I see, yes. The restriction is basically there to stop people adding `public static` members to mixins because under...

You're right this was an oversight when I was making the modlauncher agent, I had intended to do this once I figured out what mapping provider is available in modlauncher...

It seems like it could be a useful behaviour though where the injectors *are* aware of eachother, so while I don't think it's a good retrofit behaviour, it does seem...

Invokers and Accessors are very old part of the toolkit and the method signature/descriptor is not part of their identifier. Thus this is not currently supported but I will look...

I feel like there's some misunderstanding here about what this is for and how it works. For the sake of clarity, what we're talking about here is the following feature:...