IG: Durability Multiplier

[1.1.8+A-26.1.2] - 2026-06-12

Changed

• Performance Optimization: Implemented a thread-safe ConcurrentHashMap item classification cache in DurabilityHelper to cache resolved item categories, preventing redundant component scans and tag evaluations on every frame (tooltips) and every damage event.
• Compliance Sanitisation: Aligned mod comments with the Anonymity Mandate by removing references to the forbidden name from source file header comments in ClothConfigScreenHelper and DurabilityConfig.

[1.1.7+A-26.1.2] - 2026-06-11

Changed

• Performance Optimization: Refactored the durability damage reduction calculations in DurabilityHelper and ItemStackDurabilityMixin to perform item classification only once per damage event. This avoids redundant GameRule checks and tag/component inspections in the hot execution path.

[1.1.6+R-26.1.2] - 2026-06-08

Changed

• Release: Promoted Durability Multiplier to stable release stage.

[1.1.5+A-26.1.2] - 2026-06-08

Changed

• Modded Items Config Explanation: Updated the "No modded items found" explanation string on the configuration screen to clarify that standard modded weapons, tools, and armor are already automatically covered under the main categories (Multipliers and God Mode), and that only custom/uncategorized modded items are listed in the dynamic section.

[1.1.4+A-26.1.2] - 2026-06-08

Fixed

• Mod Menu Configuration GUI (NPE Crash): Fixed a crash where clicking the configuration gear in Mod Menu threw java.lang.NullPointerException: Components not bound yet. This occurred because ClothConfigScreenHelper scanned BuiltInRegistries.ITEM and queried item.getDefaultInstance().getMaxDamage() before item components were bound to their holder references. Fixed by caching discovered dynamic items during the registry freeze phase in a static list, and using item.getDescriptionId() (translatable component) instead of calling item.getDefaultInstance().
• Registry Scan (Reflection Access Exception): Fixed startup warning log spam Failed to check durability... java.lang.IllegalAccessException during item scanning. This was caused by the nested helper record DataComponentInitializers$InitializerEntry being package-private, preventing direct reflection invocation of its public methods. Resolved by calling setAccessible(true) on key() and initializer() method objects.

[1.1.3+A-26.1.2] - 2026-06-08 [CRASHING / BROKEN - DO NOT PUBLISH]

Fixed (Incomplete)

• Registry Freeze Startup Crash (Data Components Check): Rewrote dynamic scanning to use reflection on DATA_COMPONENT_INITIALIZERS to bypass early ItemStack instantiation.
• Broken / Crashing in Game:
  • Reflection Exception: Threw IllegalAccessException for every scanned item because reflected methods lacked setAccessible(true), flooding logs with warning stack traces and failing to detect dynamic items.
  • Config Screen Crash: Clicking the config button in Mod Menu crashed the client with NullPointerException: Components not bound yet due to item.getDefaultInstance() call in ClothConfigScreenHelper.

[1.1.2+A-26.1.2] - 2026-06-08 [CRASHING - DO NOT PUBLISH]

Fixed (Broken)

• Registry Freeze Startup Crash: Attempted to fix startup NPE by moving registry scanning to MappedRegistry freeze mixin.
• Crashing in Game: Crashed on startup with NullPointerException: Components not bound yet for mods that register items early before components are bound.