Activate & Stop Ability by Class

Triggers or stops abilities using a direct reference to the Ability class.

This logic is used when the exact ability is known.

Activation runs through a replicated client-authoritative flow, ensuring the ability starts correctly on owning clients.

Stopping ensures any active instance of the ability is cleanly ended across server and client, which is important for toggle abilities or those requiring manual interruption.

Server-Side Execution for ServerOnly Abilities

Executes activation and deactivation logic for abilities marked with ServerOnly Net Execution Policy.

These functions are only triggered from within the replicated net logic flow and ensure that purely server-driven abilities are started and stopped reliably without client involvement.

Used to isolate server-authoritative behavior from predicted or local-only abilities.

Client-Side Execution Net Logic

PRIVATE: Client-Side Execution of Ability Activation & Stop (Network Aware)

Handles ability activation and deactivation from the owning client, using the defined NetExecutionPolicy to determine how the logic should be executed.

Supports local prediction (Local Only), client-authoritative start (Local Predicted), and full server authority (Server Only).

If executed locally, the ability is directly started or ended based on authority.

If the policy requires server validation, a reliable RPC is sent to the server to handle the execution.

This ensures consistent and network-safe behavior for all ability types across both standalone and multiplayer setups.