CarmotShieldMixin has @Debug annotation in production jar

[unilock]

Describe the bug

This mod's CarmotShieldMixin class has the @Debug mixin annotation applied, meaning the mixin processor is set to export its target class every time the game starts. This is not necessary in a production environment. Ideally the annotation can simply be removed.

https://github.com/KonSola5/HephaestusPlus/blob/b7d10ce23a7400810455542481ff469ea6111360/src/main/java/konsola5/hephaestusplus/mixin/CarmotShieldMixin.java#L20-L22

To Reproduce

1. Install Fabric, Hephaestus, HephaestusPlus, Mythic Metals, etc.
2. Start the game.
3. The CarmotShield class is exported by the mixin processor to .minecraft/.mixin.out.

Expected behavior

That doesn't happen.

Screenshots

N/A

Crash log or game log (if applicable)

N/A

Mod List

Mod List: click to show

• Fabric API
• Hephaestus
• HephaestusPlus
• Mythic Metals
• Alloy Forgery
• owo-lib

Versions

• Loader: Fabric
• Fabric API: 0.92.1+1.20.1
• Hephaestus: 1.20.1-3.6.4.273
• HephaestusPlus: 1.1.1
• Mythic Metals: 0.19.7
  • Alloy Forgery: 2.1.2
  • owo-lib: 0.11.2

Additional context

N/A

[KonSola5]

Oops, will remove!

(This was added since at a time I couldn't get the -Dmixin.debug.export=true flag to work)