How does this affect TriggerExecute commands?
Is the trigger I've just executed put in the back of the line, or is it actually run right now as intended?
The apply-after-buff problem you've described above can be solved by registering the post-buff on a post-buff callback, if one exists. I see no reason to write the whole code in a single function.
What do you mean by registered?
Lets say I've registered a trigger T on a Roach being hit. Lets say I have two roaches, R1 and R2.
Assuming R1 was hit before R2 (or any linearization), will Galaxy process T(R1) first and T(R2) afterwards, or will it process them in parallel (thus assuming no shared state)?
Do triggers get executed in Galaxy sequentially in order of their events' arrival, or are they performed in parallel?
As much as I'd like them to run sequentially (and it is logical for an event based system that keeps track of state), in light of more recent discoveries and experiences with Galaxy I'm afraid the answer isn't obvious.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
How does this affect TriggerExecute commands? Is the trigger I've just executed put in the back of the line, or is it actually run right now as intended?
The apply-after-buff problem you've described above can be solved by registering the post-buff on a post-buff callback, if one exists. I see no reason to write the whole code in a single function.
Thanks guys! Really makes my work much easier. At least Blizz got this one right, and saved us the trouble of writing an event linearizer.
What do you mean by registered? Lets say I've registered a trigger T on a Roach being hit. Lets say I have two roaches, R1 and R2. Assuming R1 was hit before R2 (or any linearization), will Galaxy process T(R1) first and T(R2) afterwards, or will it process them in parallel (thus assuming no shared state)?
Do triggers get executed in Galaxy sequentially in order of their events' arrival, or are they performed in parallel? As much as I'd like them to run sequentially (and it is logical for an event based system that keeps track of state), in light of more recent discoveries and experiences with Galaxy I'm afraid the answer isn't obvious.