EmakiAttribute | RPG Attributes and Damage

Added

• Parent attribute system (strength / agility / intelligence). Parent attributes enter the snapshot from lore, PDC, or player point allocation, and expand into child attribute contributions by weight. Definitions gain parent_attribute: true and child_bonuses: {child: factor}.
• Attribute point system with an allocation GUI: /emakiattribute points <view|open|add|reset> for players, plus grant|set|setreset for admins. New permissions emakiattribute.points (default true) and emakiattribute.points.admin (default op).
• Configurable allocation interface gui/attribute_points.yml (CHEST, 6 rows, paged, with parent-attribute / summary / reset / page / close / border slots).
• Attribute tags and a temporary-attribute stacking mode: tags: (e.g. DEBUFF) and temporary_stack_mode: REPLACE|STACK.
• MythicMobs mechanics emaki_attribute_add, emaki_attribute_remove, emaki_attribute_add_tag, emaki_attribute_clear_tag for add/remove by effect id and bulk clear by tag. Previously only emaki_attribute and emaki_damage existed.
• Item attribute source policy attribute_sources: read_lore_attributes, read_pdc_attributes, require_lore_pdc_match. In match mode an attribute id must exist in both lore and PDC with equal values, and is counted once.
• projectile_damage_type (default projectile), switchable to physical to reuse physical-line attributes.
• same_signature_ignores_invulnerability (enabled: true, window_ms: 500): multi-hit attacks from the same attacker with the same snapshot signature and damage type no longer suppress each other via the vanilla invulnerability window.
• attack_speed.scope (global / attribute_only); attribute_only only intercepts items carrying an EmakiAttribute attack-speed attribute.
• Client health display scaling health_display_scaling (enabled: false, target: 20.0), affecting only the client-side health bar.
• release_default_data (default true); false stops generating the bundled attribute, damage type, read rule, lore format, balance coefficient, and script samples.
• Public API facade EmakiAttributeApi with resource read/consume, attribute read, equipment sync scheduling, damage application, and item contribution gate registration.
• Extension point letting third parties veto an entire item's lore + PDC contribution, complementing the existing add-only contribution provider.
• Wholesale copying of PDC attribute payloads between items with selected sources excluded.
• Action system integration for attribute sync, resource consume, resource modify, and temporary attribute tag actions.

Changed

• Stricter attribute definition validation that reports configuration errors instead of failing silently: child_bonuses on a non-parent attribute, pointing at a non-existent child, a parent pointing at a parent, and damage-type stages referencing a parent attribute directly.
• Config precheck text and trace/debug field labels are localized.
• Message prefix switched to a new brand gradient.
• api-version raised 1.21 -> 1.21.8. Dependencies declared in Paper's structured form: EmakiCoreLib required; MythicMobs / PlaceholderAPI / MMOItems optional. Build base moved spigot-api -> paper-api; Java target unchanged at 25.

Fixed

• Damage feedback showed the attacker as a raw vanilla enum name (e.g. ZOMBIE); it now resolves a readable name, using the player name for players.
• Config precheck results were unreadable for non-English owners because the text was hardcoded English.

Removed

• The browser-based Web Console layer (web-console.yml, the locale web extension, the whole frontend project). Owners who used it for attribute diagnostics or config editing must use commands instead.
• The descriptor commands: section, following the plugin.yml -> paper-plugin.yml migration; commands register at runtime.
• Support for plain Spigot. Only Paper-family servers can load the plugin.

Notes

• Requires EmakiCoreLib 4.6.0. Update CoreLib first.
• Servers below 1.21.8 are unsupported. folia-supported: true was already declared before this release.
• All new config keys ship with defaults, so an existing config loads as-is and gets filled in; no manual migration is required.
• After updating, verify /emakiattribute points open, attribute snapshots, and damage resolution, and move any Web Console diagnostics over to commands.