Current Capability Status
This table reflects FTK2.ModAPI 0.5.9 and actual FTK2 1.14.6 evidence.
| Feature | Status | Current boundary |
|---|---|---|
| Mod registration, dependencies, owner context | Runtime proven | Main-thread owner registration and isolation |
| Namespaced content IDs | Runtime proven | Stable owner-qualified IDs |
| Lifecycle, GameDataReady, events | Runtime proven | Generation-aware main-thread events |
| Logging and diagnostics | Runtime proven | Owner-scoped logs and text state dump |
| Custom items and native activation | Runtime proven | Template-based definitions |
| Weapon/armor/accessory/consumable properties | Runtime proven | Supported typed override surface |
| Localization and template visual aliasing | Runtime proven | Existing presentation resources are reused |
| Inventory and equipment consumer paths | Runtime proven | Tested with installed definitions |
| Custom ability registration/activation | Runtime proven | Namespaced native ability clones |
| Ability tooltip/presentation/icon | Runtime proven | Native inventory card path |
| Equipped ability enumeration | Runtime proven | Custom weapon plus SkillRollData |
| Combat ability availability | Runtime proven | Visible, enabled, selectable action |
| Native custom ability execution | Runtime proven | Correlated enemy HP damage |
| Existing status/passive references | Supported | Refer to native definitions only |
| Installed-definition save paths | Partially / runtime tested | Inventory, equipped, adoption, and missing-content safety paths passed; broad capability remains false |
| Multiplayer | Unverified | No synchronization or parity guarantee |
| New passive definitions | Planned (0.6.x) | Not public in 0.5.9 |
| New status-effect definitions | Planned (0.6.x) | Not public in 0.5.9 |
| Custom traits | Planned (0.6.x) | Not public in 0.5.9 |
| Custom classes, enemies, pets | Unsupported | No current public API |
| Custom quests, encounters, recipes | Unsupported | No current public API |
CustomItemCapabilities.SavePersistence and CustomAbilityCapabilities.SavePersistence remain false. The tested save paths are valuable evidence, but do not constitute a universal persistence promise.