Add the following to the second paragraph of “Timed Actions”

Each Timed Action has a unique Identifier, which is a flavor-text string of no more than 10 Case Insensitive Alphanumeric characters. Whenever a City or Capital initiates a Timed Action, they must also declare an Identifier for that action which does not match the Identifier used for any other Timed Action. A list of which timed actions have been initiated, including who initiated them what kind of action it was, when the completion time was and what it’s Identifier is should be publicly tracked

Add a new sub-rule to Timed Actions called “Queued Actions”

The Action Queue consists of an Target Identifier, the name of a City or Capitol (the performer), and the action they would like to perform as well as any inputs needed to be able to perform that action. Timed Actions in the Action Queue are considered to have the identifier specified as input and must satisfied the same uniqueness rules, and are considered to be unresolved. However they do not have a completion time.

A City or Capitol may add an action to the action queue with themselves as the Performer at any time, provided they specify the Target Identifier as an Identifier of a Timed Action or Queued Action which has not yet been resolved, and which they do not already have an Action with that Target Identifier in the Action Queue.

A City or Capitol may remove any action from the action queue with themselves as the Performer at any time.

Whenever a Timed Action is resolved, any actions in the action queue with that Timed Action’s identifier as its Target Identifier are immediately performed on behalf of the performer of that action. If multiple actions would be performed in this manner, the order they are performed is randomly determined. Once a queued actions has been performed it is removed from the action queue.