Custom Items

Custom-item work is one of the most mature areas of the toolkit. Earlier 0.5.x evidence proves the public definition/activation path, namespaced identity, localization, visual aliasing and multiple save-related invariants. The latest retrieved 0.5.4 run did not enable every custom-item test group, so this documentation preserves the distinction between implemented and runtime proven rather than treating a skipped run as a regression.

Proven areas across the current development line

• independent custom definition creation from real FTK2 templates;
• custom definition registration through the public custom-item service;
• owner-tracked session activation and typed activation state;
• English localization registration/resolution;
• template/visual alias registration;
• FTK2 save serialization retaining custom ConfigName and Thing.Id;
• installed-definition preflight before load;
• loaded custom-Thing adoption in real runs;
• missing-definition detection and blocked-load recovery in dedicated tests.

Still document conservatively

Weapon, armor, accessory and consumable gameplay-property helpers exist in the development line, but the latest 0.5.4 run available to this documentation had that dedicated property test group disabled. Those pages should be expanded from source/audit files when the source checkout is connected.