Custom Abilities

Custom abilities/attacks are implemented far enough in 0.5.4 to be registered and activated as native FTK2 ability data, resolved by namespaced identity and referenced by custom items. They are not yet documented as fully accepted end-to-end combat support because the latest retrieved manual consumer run did not clear every downstream boundary.

Runtime proven in 0.5.4

• compatible real FTK2 ability-template audit;
• three independent namespaced custom ability definitions;
• native activation in the FTK2 ability/presentation databases;
• custom identity lookup through native consumers;
• typed property readback for attack and consumable-style abilities;
• references to existing FTK2 status/effect definitions;
• source templates remain unchanged;
• custom item → custom ability dependency resolution;
• invalid existing-status reference rejection before partial insertion;
• owner isolation;
• dependency-safe deactivation refusal while an active item references an ability.

Acceptance boundary still open

In the latest 0.5.4 evidence, the real item-tooltip test reached presentation, skill-roll, icon and name resolution, but description resolution failed. Because that prerequisite failed, equipped weapon action enumeration and combat action availability were skipped, and no qualifying manual native Flame Cleave execution was observed.

Treat those downstream paths as Experimental until a later runtime result proves them.