Downtime submissions can be a great way to add more flavor to your character, fill in gaps in information, and utilize assets and resources not necessarily available during games. During downtime characters may travel, gather information, explore, or perform numerous other types of actions to support the stories told at our games. Combined with personal modules and a proactive approach during games, downtime actions can be a worthwhile and rewarding pursuit. However, we do have a limited amount of time and energy to devote to handling downtime requests, so we ask that the following guidelines be used when sending in your downtime submissions.
The staff will assume a character is doing nothing of value in downtime unless we receive a submission that says otherwise. Even if the character performs the same actions every time or is continuing to work towards a previously described goal, we still require a submission stating so explicitly.
Downtime submissions must be received at least two weeks prior to the next game. The longer and more ambitious the action you wish to undertake, the sooner we need to receive it and the more details need to be included. Submissions will not be responded to immediately; it takes time for us to review and approve a response.
Long-distance travel is time-consuming, and it may be impractical for a character to attempt to reach certain locations during downtime unless they have access to alternate means of travel. If the character does have access to such means they should be explicitly referenced.
The writers reserve the right to reject all or part of any downtime submission received. There are numerous reasons for this, most often being that the action is not suitable for downtime and needs to happen during a game. In any case, if your downtime request is rejected you will receive an explanation of why.
A summary of immediate and relevant goals should be placed in bullet point format at the top of your request followed by a more detailed description of the actions, precautions, and materials used by the character in order to accomplish these goals. Including how much time the character dedicates to the task is also helpful.
Be sure to phrase your requests in a down time as a potential intended action, not one with expectations of certain outcomes. As success is not a certainty in a downtime, as much as it is in Uptime, we ask players Phrase their goals along the lines of:
“Bob the Ork would like to learn more about Gardening. He will attempt to plant some flowers and water them, using a nearby well for water source. He would like to try to raise tomatoes primarily, but only knows how to raise squad so he is somewhat out of his wheelhouse of skills.”
The request should reflect a desire to attempt actions, not a request for an action to take place or for an intended consequence to be met.
The writers will do their best to provide a realistic and informed response to your downtime submission; be warned, however, that if a character is portrayed as clumsy, oafish, and unsubtle, for example, attempts at stealth based downtimes may have less than spectacular results for the character. Writing in your downtime that your character does something ‘intelligently’ (“I investigate the place in whatever way is most effective”) will not increase your chances of success, but outlining your plans in detail (“I case the place for several days before attempting their break in to find out when the most guards are asleep/drunk”) will help us, and you as well.
Finally, remember that downtime actions are intended to help support the stories we tell at our games; it is designed to enhance the events which take place during games, not replace them. As such, if we feel you are acting beyond the scope of a downtime action we will tell you so and ask that you scale back your request.
Downtimes must be turned into plot no later than 2 weeks prior to the upcoming event.