HyArmorVariants

Fixed

• Combat owner API — ArmorVariantsApi.isActiveCombatOwner() now returns true only when the plugin is enabled and combat ECS systems registered successfully (combatSystemsRegistered). If registration throws in setup(), the flag stays false so HyWeaponVariants is not told to yield to a non-functional pipeline.
• Thorns/defender when damage source has no entity ref — Some PvP or other damage sources do not carry an attacker entity ref. The handler now uses attackerRefForApply as fallback for Thorns (3b) and reuses armorEffectAttackerRef for defender armour special (4b), so defender effects still proc when the source lacked a ref but a valid attacker can be resolved.
• Thorns/defender on projectile hits — Skeleton (or other) projectile damage may use a source that is not EntitySource. The damage system now tries getShooterRef(), getOwnerRef(), getSourceRef(), and similar methods on the source so the shooter is resolved and armour-on-attacker effects apply to the correct entity.
• Armour tooltips in DynamicTooltipsLib — Armour items were sometimes skipped by the weapon blacklist. Tooltip logic now computes isArmour before the weapon blacklist check so armour always gets variant tooltips.
• Durability overwrite on variant apply — When applying or refreshing variants, the code now early-outs if the stack already has the correct max and current durability, avoiding unnecessary overwrites.

Changed

• Startup logging — Logs now include combatSystemsRegistered=true/false, whether HyWeaponVariants was detected on the classpath, and whether the /hwv alias was registered or intentionally suppressed (with reason). Makes it clear who owns combat and which command is active when both mods are installed.