Overview

WCGASTransferSubsystem is a Tickable World Subsystem that serves as the central tracking and coordination system for all active effect and ability transfers in the Wonderscape GAS Ally plugin. It automatically initializes when the game world starts, registers and tracks all active transfers using O(1) TMap lookups, handles multiple expiration types (timer-based, range-based, death-based, logout-based), manages ownership chain tracking for multi-step transfer scenarios, coordinates with the Ability Grant Registry for duplicate-aware ability management, and provides comprehensive dead owner handling with configurable fallback behaviors.

Purpose

The Transfer Subsystem orchestrates all effect and ability transfer tracking by providing:

• Automatic Initialization: Initializes on game world startup, sets up periodic cleanup timers, and subscribes to GameMode logout events
• Effect Transfer Registry: TMap-based storage (TransferID → FWCGASTrackedEffectTransfer) enabling O(1) registration, lookup, and unregistration
• Ability Transfer Registry: TMap-based storage (TransferID → FWCGASTrackedAbilityTransfer) with identical O(1) performance characteristics
• Multi-Expiration Support: Timer-based (Timed), proximity-based (WhileInRange), lifecycle-based (UntilDeath, UntilLogout), and permanent duration types
• Range Checking System: Tickable range verification for WhileInRange transfers at configurable intervals (default 0.5s)
• Ownership Chain Tracking: Complete history of all holders (FWCGASOwnershipChain) enabling return-to-source, return-to-origin, and chain-walking operations
• Dead Owner Handling: Four configurable behaviors (Remove, ReturnToNextValid, KeepOnHolder, TriggerDelegate) for when return targets are invalid
• Death/Disconnect Integration: Automatic cleanup on actor death (via NotifyActorDeath) and player logout (via FGameModeEvents::GameModeLogoutEvent)
• Event Delegates: Blueprint-assignable delegates for transfer, return, expiration, and dead owner scenarios
• Debug API: Development-only functions for inspecting active transfers and tracking state

How It Works

Initialization Flow

1. World Subsystem Startup: When the UWorld initializes (Game, PIE, or GamePreview world types), the subsystem automatically creates via UE's subsystem lifecycle
2. Setup Cleanup Timer: Creates a 30-second looping timer that calls CleanupStaleEntries() to remove transfers with invalid ASC weak references