Bureaucrats, developer, Administrators
10,625
edits
No edit summary |
No edit summary |
||
Line 7: | Line 7: | ||
When a group of writers post, it can become difficult to keep track of the posts once a few start coming in; this is compounded by the fact that not every post is written in strict chronological order- we use flashbacks, flash forwards, and other tools when creating our stories. Having an updated mission timeline becomes an indispensable tool in keeping track of what is happening when during a mission. | When a group of writers post, it can become difficult to keep track of the posts once a few start coming in; this is compounded by the fact that not every post is written in strict chronological order- we use flashbacks, flash forwards, and other tools when creating our stories. Having an updated mission timeline becomes an indispensable tool in keeping track of what is happening when during a mission. | ||
<pre> | <pre> | ||
Line 23: | Line 21: | ||
*NOTE: The "Mission SD" is the actual SD on which the action of the post takes place. IT IS NOT THE SD OF | *NOTE: The "Mission SD" is the actual SD on which the action of the post takes place. IT IS NOT THE SD OF | ||
WHEN IT WAS WRITTEN. Those are two completely separate things; just because a post was written on SD 350630 | WHEN IT WAS WRITTEN. Those are two completely separate things; just because a post was written on SD 350630 | ||
(June 30, 2435/2023) does NOT mean that is when the action takes place | (June 30, 2435/2023) does NOT mean that is when the action takes place. | ||
You do not have to worry about figuring out the Mission SD- as long as you are careful about your MD, I will | You do not have to worry about figuring out the Mission SD- as long as you are careful about your MD, I will |