Hi all, please tell me I'm missing something obvious here. Given:
Instead of waiting: try the first stored action; try the second stored action.
..I would like to do something generic (i.e., not tied to what the action actually is) when either or both of these fail. The last one is easy -- an Every Turn rule can capture it regardless whether it succeeds or fails. And I can capture the first one's success with an After rule. But how do I capture the first one's failure? The After rules won't run since it failed, the Every Turn won't run in-between the Tries, Unsuccessful Attempt By won't run for anything not an NPC request, and the Check and/or Instead rules are the ones deciding the failure to begin with, and *they* are called from different rulebooks themselves.
Where do failed actions go after an Instead or Check rule plonks them?
> Hi all, please tell me I'm missing something obvious here. Given:
> Instead of waiting: > try the first stored action; > try the second stored action.
> ..I would like to do something generic (i.e., not tied to what the > action actually is) when either or both of these fail. The last one > is easy -- an Every Turn rule can capture it regardless whether it > succeeds or fails. And I can capture the first one's success with an > After rule. But how do I capture the first one's failure? The After > rules won't run since it failed, the Every Turn won't run in-between > the Tries, Unsuccessful Attempt By won't run for anything not an NPC > request, and the Check and/or Instead rules are the ones deciding the > failure to begin with, and *they* are called from different rulebooks > themselves.
> Where do failed actions go after an Instead or Check rule plonks > them?
> -Ron
Nevermind. I found it.
Instead of waiting: try the first stored action; if the rule failed, say "FAILED."; if the rule succeeded, say "SUCCEEDED."; try the second stored action. if the rule failed, say "FAILED."; if the rule succeeded, say "SUCCEEDED.";
|
