GameplayAbilities and you

[anonymous_user_843b99c6]

@iniside;725768

AbilityTasks, are more or less standard async K2Nodes. This is the file which define them:
K2Node_LatentAbilityCall.cpp
You can have specialized K2Nodes for any tasks if you wish (limiting them to specific graphs, generating outputs, having graphs inside K2Node, pretty much anything goes).

Though creating custom K2Nodes is bit obscure, since that part of engine have zero documentation, all you can do is to looks for how it is done and reverse engineer it.

Ah thanks. This will be useful to know when I want to pull some more details out about how exactly they for example work and convert their delegate into output pins. The actual logic in the AbilityTasks themselves seems thankfully rather straightforward, most of them just bind some delegates in the Activate function and wait for them to get called by the component/objects responsible for them.