Joseph Burton

You probably should have asked before doing this. DemonWav is doing a refactor to the project creator system, which means you will have to mostly rewrite this.

This should be fairly easy to implement.

My two cents: it would be a bit of a maintenance burden.

Have you tried changing the priority relative to the mixin which adds the field?

This is intended behaviour, although I agree that it's poorly documented in the Javadocs

I had the same thing happen to me a couple of days ago. Do we know if this issue is in Mixin itself, the Mixin AP, or in Fabric loom?

Appears to be caused by [this check](https://github.com/SpongePowered/Mixin/blob/4585277f9f4b026065ce749f279ea1ad4919c4f1/src/ap/java/org/spongepowered/tools/obfuscation/AnnotatedMixinElementHandlerAccessor.java#L176) in the AP, where it is checking the UpperCamelCase target class name against the lowerCamelCase accessor name. Probably best to remove the name...

Imo a predicate is a function, so `IS_FOOD` makes the most sense to me, and fits with the style I tend to go with in my personal code.

Java 14 is the latest LTS Java version, so it still makes sense to use it.

Oops