Probably doesn't matter but I'm not sure. [Skipping mixins warning]
K0-RR opened this issue ยท 1 comments
I'm getting this on mc load
[11:37:26] [main/WARN]: @ModifyConstant conflict. Skipping mixins.tweakeroo.json:MixinCloneCommand->@ModifyConstant::getBlockCountLimit(I)I with priority 999, already redirected by carpet.mixins.json:CloneCommandMixin->@ModifyConstant::fillLimit(I)I with priority 1000
[11:37:26] [main/WARN]: @ModifyConstant conflict. Skipping mixins.tweakeroo.json:MixinCloneCommand->@ModifyConstant::getBlockCountLimit(I)I with priority 999, already redirected by carpet.mixins.json:CloneCommandMixin->@ModifyConstant::fillLimit(I)I with priority 1000
[11:37:26] [main/WARN]: @ModifyConstant conflict. Skipping mixins.tweakeroo.json:MixinFillCommand->@ModifyConstant::getBlockCountLimit(I)I with priority 999, already redirected by carpet.mixins.json:FillCommandMixin->@ModifyConstant::fillLimit(I)I with priority 1000
[11:37:26] [main/WARN]: @ModifyConstant conflict. Skipping mixins.tweakeroo.json:MixinFillCommand->@ModifyConstant::getBlockCountLimit(I)I with priority 999, already redirected by carpet.mixins.json:FillCommandMixin->@ModifyConstant::fillLimit(I)I with priority 1000
As long as both mods have the same feature of overriding the block count limit in those commands, you will get this warning, as one of the mods is going to fail to apply the mixin, as the other one already did.
There is nothing that can currently be done about this AFAIK. And it's otherwise harmless, it just means that Tweakeroo's tweak for overriding the limit does not work, as Carpet is the one that changed the code. So you would need to use this feature (increasing the fill or clone command limit) via Carpet.