Current Capability Status
This matrix is intentionally conservative and is based on the latest retrievable 0.5.4 runtime evidence plus earlier development-line tests where the relevant 0.5.4 group was disabled rather than failed.
| Capability | Status | Notes |
|---|---|---|
| API startup/version/main-thread lifecycle | Runtime proven | Current 0.5.4 startup tests pass. |
| Mod registration / lookup / owner context | Runtime proven | ExampleMod startup path passes. |
| Logging and diagnostics | Runtime proven | BepInEx sink handoff and diagnostics availability pass. |
| Namespaced IDs / owner isolation | Runtime proven | Cross-owner custom-ability operation is rejected. |
| Custom item definition + public registration | Runtime proven | Proven in development-line runtime tests. |
| Custom item activation | Runtime proven | Owner-bound activation result/handle proven. |
| Custom item localization | Runtime proven | Name and description resolution proven. |
| Template/visual aliasing | Runtime proven | Alias registration proven; individual live consumer visuals remain version-sensitive. |
| Save serializer custom identity | Runtime proven | ConfigName, Thing.Id and material serialization tested. |
| Installed-definition load preflight | Runtime proven | Compatible loads observed. |
| Missing custom-content block/recovery | Runtime proven | Dedicated missing-definition run proves blocked commit and safe recovery. |
| Custom ability registration/activation | Runtime proven | 0.5.4 passes registration, activation and identity lookup. |
| Existing status/effect references | Runtime proven | Existing FTK2 definitions can be referenced. |
| Item → custom ability dependency | Runtime proven | Dependency resolution and deactivation protection pass. |
| Ability tooltip description | Experimental | Latest retrieved 0.5.4 manual test fails description resolution. |
| Equipped custom-ability action enumeration | Experimental | Not reached after tooltip prerequisite failed. |
| Combat availability / native manual execution | Experimental | Not runtime proven in latest retrieved run. |
| Multiplayer | Unsupported / unproven | No public runtime proof. |
| Custom classes | Unsupported | Not a current public capability. |
| Custom enemies | Unsupported | Not a current public capability. |
| Custom pets | Unsupported | Not a current public capability. |
| Custom quests / encounters / recipes | Unsupported | Not current public capabilities. |
| Custom passive definitions | Planned | Existing references are different from defining new passives. |
| Custom status-effect definitions | Planned | Existing references are supported; new definitions are not public/proven. |
| Custom traits | Planned | Future milestone, not current public API. |
Rule for release documentation
A capability moves to Runtime proven only when the relevant real-game test or accepted manual consumer path succeeds. Implementation alone is not enough.