Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="tentfox" data-source="post: 5398611" data-attributes="member: 58988">I am not going to go entirely with the stack method, but I do like the way you broke down an action into atomic sub actions.Here is what I am thinking:- Each action is built up of sub actions and action flows, and each of those can likewise be broken up. While this seems complex in most cases it will be as simple as an attack action is an attack roll which flows on to a damage roll on the condition of a hit, but allows for far more complex actions.- Each action, and therefor sub action can potentially have interrupts and reactions. To model this before each action/sub action is performed I will gather all potential interrupts and resolve them in initiative order. Any of these actions will need to recursively go through this same process.- After the interrupts are resolved attempt to perform the original action/sub action, testing for validity as an interrupt may have changed the condition of this succeeding (ie the performer is now dead or out of range).- Now compile a list of all potential reactions and resolve them in initiative order, once again doing this recursively.- Once the action or sub action has been completely resolved in this manner move on to the next action in the chain based on the final result of the first action.And then this is further complicated by the granulation of these actions and sub actions. Potential interrupts could not just be being attacked, but being hit by an attack. So the chain might be, attack roll (result hit) -> hit (result ok)-> damage. This is easily going to be the most complicated part of this.</blockquote>

Verification