Trinkets Compat Layer for Accessories

Trinkets Compat Layer for Accessories

3M Downloads

Mixin Conflict in Accessories Mod

tianyeorg opened this issue ยท 1 comments

commented

I encountered a Mixin warning while launching Minecraft with Accessories Mod (version 1.2.17-beta+1.21.4) on Fabric Loader 0.16.10. The warning states that a Mixin injection exceeds the allowed shift value, which may affect item NBT processing.

logs:[17:00:07] [main/WARN]: @Inject(@at("INVOKE")) Shift.BY=2 on accessories-common.mixins.json:NbtCompoundMixin from mod accessories::handler$zzo000$accessories$adjustCheckForListVariants exceeds the maximum allowed value: 0. Increase the value of maxShiftBy to suppress this warning.

Additionally, there are Mixin conflicts with other mods such as Not Enough Animations:[17:00:31] [Render thread/WARN]: Method overwrite conflict for setEntity in notenoughanimations.mixins.json:LivingRenderStateMixin from mod notenoughanimations, previously written by io.wispforest.accessories.mixin.client.LivingEntityRenderStateMixin. Skipping method.

Steps to Reproduce

Install Accessories Mod (1.2.17-beta+1.21.4) on Fabric Loader (0.16.10).
Launch the game with multiple mods, including Not Enough Animations.
Observe the Mixin conflict warnings in latest.log.
Expected Behavior
The mod should initialize without Mixin errors, and accessories should work properly.

Actual Behavior
The Mixin system reports an invalid shift value (Shift.BY=2), which could lead to NBT data issues or mod malfunctions.

Possible Solutions

  • Update the Mixin to respect the allowed shift values or modify maxShiftBy in the mixin configuration.
  • Check for compatibility issues with Not Enough Animations and other mods affecting LivingEntityRenderStateMixin.
  • Ensure the mod is compatible with the latest Fabric Loader.

Environment

  • Minecraft Version: 1.21.4
  • Fabric Loader Version: 0.16.10
  • Accessories Mod Version: 1.2.17-beta+1.21.4
  • Other Installed Mods: (List key mods, e.g., Not Enough Animations, Fabric API, etc.)
commented

A fix for the mixin collision has been dealt with, and the shift error is only a warning; it will be fixed in the future.