PowerWeave attaches reusable gameplay abilities to existing Nexo item IDs. Nexo supplies the item visuals and resource packs; PowerWeave owns bindings and ability execution. Abilities stay in separate YAML files, so an item can acquire new behavior without duplicating its Nexo definition.
Active and passive abilities
Right-click, sneak-right-click, melee hits, and projectile impacts enter the ability pipeline. Right-click bindings work from either hand, including shields. The current documentation also covers equipped and inventory passive triggers, evaluated periodically and throttled through cooldowns.
Conditions & targets
Conditions can restrict activation by permissions, world, chance, health, and sneaking state. Ability-level targets establish a default; individual actions can override it to affect the actor, a direct target, a looked-at entity/location, or nearby entities.
Composable actions
Combine damage, healing, potion effects, movement, lightning, particles, sounds, and messages. Projectile launch is an action; entity/block impact triggers are separate abilities. Tagged projectiles launched by PowerWeave or fired/thrown from Nexo items carry their binding context into impact handling.
Scoped cooldowns
Cooldowns can belong to a player/ability, player/item, or player/item/ability combination. Held-item feedback uses actionbars, bossbars, or optional PlaceholderAPI values. Passive cooldowns throttle execution without appearing in that held-item feedback. Cooldown state is in memory and resets on server restart.
Binding-level item behavior
Bindings can add runtime enchantments, lore presentation, tooltip visibility, and glint. Bound-item retention on death can be configured globally and overridden per binding. These settings apply to Nexo item IDs rather than a persistent ability state for each individual item instance.
Validation and administration
Commands and the editor browse the Nexo catalog, manage bindings, create ability shells, and inspect loaded behavior. Validation reports malformed files; a rejected reload retains the previous valid ability/binding configuration. Diagnostics identify missing abilities and orphaned item IDs without deleting bindings. Complex action and condition editing remains YAML-based.
Requirements and current scope
PowerWeave requires Paper and a separately installed Nexo plugin. The wiki documents a 1.21.4 minimum within the supported range, Java 21 for Paper 1.21.x, and Java 25 for 26.x. PlaceholderAPI is optional; consult the documentation for compatibility and configuration details.
The project remains in public beta. A full visual node editor, delayed/repeating action chains, homing projectiles, database storage, and a public extension API are outside the current implementation.
Development note
The Beta 0.2 devlog documents the earlier projectile, cooldown-feedback, and runtime-enchantment work.
