Modifications on DPF

[vinymayan]

API Changes

• Bumped DPF::InterfaceVersion to 4.
• Preserved the existing vtable order for backwards layout stability.
• Added ownership-aware slot APIs at the end of the public interface:
  • CreateByTypeForOwner(const char* owner, const char* key, uint32_t formType)
  • GetOrCreateByOwnerKey(const char* owner, const char* key, uint32_t formType)
  • ReleaseByOwnerKey(const char* owner, const char* key)
  • ReleaseByLocalId(uint32_t localId, const char* owner)
  • ReleaseOwner(const char* owner)
• Added equivalent Papyrus native wrappers for the new ownership APIs.
• Existing anonymous APIs remain available:
  • CreateByType(formType)
  • GetOrCreateByLocalId(localId, formType)
  • GetOrCreateByFormId(formId, formType)

Global Registry Behavior

• Data/SKSE/Plugins/DPF.json is now the single global registry for DPF FormID slots.
• Registry schema was upgraded to schemaVersion: 2.
• Slots now store ownership metadata:
  • localId
  • formType
  • state
  • owner
  • key
• The stable identity is still the ESP-local localId, not the full FormID.
• Full FormIDs are recalculated from the current load order of Dynamic Persistent Forms.esp.

Ownership Rules

• owner + key uniquely identifies a named slot.
• GetOrCreateByOwnerKey(owner, key, type):
  • returns the existing form if the same owner/key/type already exists;
  • returns nullptr if the owner/key exists with a different type;
  • allocates and registers a new slot if no matching slot exists.
• CreateByTypeForOwner(owner, key, type) follows the same owner/key behavior.
• Anonymous APIs continue to create slots with empty owner and key.
• A slot cannot be reused with a different formType.

Release / Cleanup Behavior

• ReleaseByOwnerKey(owner, key) removes a single owned slot.
• ReleaseByLocalId(localId, owner) only releases the slot if the owner matches.
• ReleaseOwner(owner) removes all slots owned by that owner and returns the number released.
• Released runtime forms are marked deleted when present.
• Released slots are removed from DPF.json, making those local IDs available again.

Schema Handling

• No compatibility or migration is provided for older registry schemas.
• If DPF.json is missing, invalid, or not schema 2, DPF starts with an empty registry and rewrites the file using schema 2.
• Old registry data is intentionally ignored to avoid mixing incompatible slot ownership rules.

Consumer Mod Flow

• Mods should prefer GetOrCreateByOwnerKey(owner, key, formType) for stable owned slots.
• The consumer mod remains responsible for defining what the form does.
• Recommended flow:
  • request or recover a slot using owner + key;
  • store the key/localId as needed;
  • reapply perk/spell/item data on load;
  • call release APIs when the owned slot should be freed.

[vinymayan]

Remember to when build remove the logger info of when save stuff since i was testing on release 🫠