https://github.com/ItsThosea/BadOptimizations/blob/cf6c12acc56873a462ebd8682c4c368498eb3f60/common/src/main/java/me/thosea/badoptimizations/mixin/entitydata/MixinEntity.java#L89-L94

things like this auto-cancel
meaning mods which e.g. in this case make entities glow when the player has certain effects (or enchantments) (so it's visual only for that player, not a persistent state affecting all players) would no longer apply

(i know this can be avoided using the priority but that usually just stays at the default of 1000)
i did notice your default is 1200

i ran into some issues since i used RETURN to skip redundant logic

that actually might be the wrong method for that kind of purpose, since at times it does update the glowing status on the server side

i switched to Minecraft#shouldEntityAppearGlowing

oh wait you saw that lmfao

Anyway, I think I might just remove those optimizations completely and use a faster array in DataTracker to compensate?

i meant my code / idea with "wrong method for that kind of purpose" btw
(since whatever you return there can lead to server updates, so it's not fit for client-only logic)

(i got an email about your comment though if you're curios)

i meant my code / idea with "wrong method for that kind of purpose" btw

(since whatever you return there can lead to server updates, so it's not fit for client-only logic)

(i got an email about your comment though if you're curios)

I mean there's always @WrapOperation from MixinExtras, basically @Redirect but conditional and stackable with other mods.

Fixed in 1.6.4, don't know when I'll release it tho, I still have some other bugs to fix.
I replaced each injector with @Overwrite since it stacks with @Inject and very few mods will @Redirect on the data tracker get call.