Closed 3th3 closed 3 years ago
The reflex enchantment modifies the same constant value as I do (in my mod) to block instantly. I guess we can solve this compatibility issue by setting different priority levels for our changes but I'm not sure about it as I never did this. I'll check that a bit later and tell you
I'll look into this on my end as well, I will see if I can do away with the ModifyConstant entirely as to avoid this issue in the future
I have addressed this particular compatibility issue in the latest alpha release. I will let this issue remain open until I publish an official release.
Good, I'll do the same change to my mod I guess so that mine won't have the issue with another mod doing the same. Thanks
I have addressed this particular compatibility issue in the latest alpha release. I will let this issue remain open until I publish an official release.
Thanks bunches! Happy to know I can use both of these mods at once again when the update releases
I won't log the crash report. There is no need to, here is the important snippet. @ModifyConstant conflict. Skipping extra_enchants.mixins.json:LivingEntityMixin->@ModifyConstant::applyReflex(I)I with priority 1000, already redirected by sihywtcamc.mixins.json:shield.LivingEntityBlockingMixin->@ModifyConstant::instantlyBlock(I)I with priority 1000
Seems simple enough, reflex is conflicting with instantblock. The conflicting mod is https://www.curseforge.com/minecraft/mc-mods/sihywtcamc#c37. I don't think instantlyBlock is an enchant, however. Its supposed to be a new trait to shields in general.