Hello, i’ve encountered some weird behavior with the GAS system, particularly adding a hit result to an effect context, that i am trying to understand.
im trying to spawn a gameplay cue actor with hit data at the location of a projectile impact. here was my logic, summarized:
1.) the firing ability spawns projectile, and feeds it the effect spec handle on spawn.
2.) projectile detects the hit and applies the spec
3.) projectile executes the cue
the cue needs hit data, so we have to add that to the parameters, aka the effect context. so we should be able to take our spec, get the effect context, promote it to a variable, add the hit result to it, and shazzam, we have a context with hit data ready to pass to the cue.
however i quickly found that this was not the case. the context contained no hit data.
the chain was as follows
ability makes spec->spawn projectile and pass it spec->projectile creates context from that spec->promote to variable, addhitresult node.
this didnt work.
but this did:
ability makes spec->ability makes context->spawn projectile and feed it spec and context->addhitresult to the context
im sorry but this makes no sense to me at all. how is
ability spec->ability context->projectile
fundamentally different from
ability spec->projectile->projectile context?
is there some key principle im missing? perhaps a networking issue? if anyone has any idea please let me know, im trying my best to understand this system at its core.
