Definition & Activation Model

The custom-item model separates a definition from its runtime activation. That allows ModAPI to validate ownership and dependencies before inserting/activating native FTK2 runtime content.

The development-line runtime tests demonstrate:

  • lookup of a real FTK2 template;
  • creation of an independent custom definition;
  • clone isolation from the source template;
  • public registration/readback through the custom-item service;
  • activation with an owner-bound handle/state;
  • preservation of the source template.
  1. Register localization needed by the definition.
  2. Register the namespaced custom-item definition.
  3. Ensure referenced abilities/passives already exist when applicable.
  4. Activate the definition for the current game-data generation.
  5. Retain the activation handle for status/cleanup.

Exact SDK signatures will be generated from current XML comments; this page intentionally describes the proven lifecycle without guessing method names.