Saga Core
First, freedom. Do what you like. While a main pathway will be provided in the form of straightforward, army-based combat, there are opportunities for creative risk-taking. Acting as a double-agent, assassinating an enemy general, sabotaging another member's Militia endeavors, etc.; the world is literally open to you.
Second, other-ness. The Chubbs universe is not merely a reflection of your characters, but involves dangers and wills external to your charaters'. This world is dangerous and chaotic, doubly so in a time of intergalactic warfare. The planets spin on, whether you observe it or not.
Saga Structure
Of course, not all endeavors will succeed. Ambitious aims will require ambitious (and consistent) roleplaying.
To reflect the malleability of the story, and the impact of the individual characters, the saga will consist of a series of four-day cycles. For the entirety of the first three days of a cycle, as well as the fourth day (up to 6 PM EST), roleplaying may occur. But, on the fourth day, after 6 PM EST, the saga will be temporarily closed (this will be referred to as a 'Closure'). During this period, the saga architects (which includes myself, Vad, and Kaden) will update every thread currently active in the saga. Sometimes these updates will be substantial, such as the resolution of a fight, or an evaluation of a particularly significant endeavor. Sometimes these updates will be without substance: 'the battle rages on.' If you make waves, you can expect more substantial updates.
Closures will be scheduled regularly (with a definitive calendar set up shortly). These Closures may take up to, but will take no longer than, midnight. of the same day.
Because of the nature of Closures and Updates, roleplays during the Closure period run the risk of being negated by Updates. If a roleplay is negated (that is, the roleplay contains material rendered illogical or irrational, such as referencing the actions of a character killed off in the Update), then that roleplay will be deleted (after giving the member a chance to save it, in case portions of it can be salvaged). This will be relatively uncommon, but it is nevertheless something to consider. Do not plan out your roleplays too far in advance, particularly if involved in a chaotic environment (such as defending a besieged spaceport); anything can happen, and plans can go awry.
Further, during an Update, there will be multiple buffs and debuffs. All of these will have at least some effect upon your endeavors. For example, if you shoot for an ambitious goal, and meet that goal, you will likely gain a buff (such as increased morale for any troops following you, or increased combat prowess for a short time due to recent victories). If, however, you shoot for an ambitious goal and do not roleplay accordingly, you will likely gain a debuff (such as a broken arm in a combat situation, or decreased troop morale). These will be catalogued and updated in a dedicated topic in the Invasion Discussion sub-forum, organized by member.
Because of the specificity and regularity of Updates, it is important that all saga threads are organized correctly. To this end, consistency of location for members involved in a particular storyline is all important. If you are participating in this saga alone (with perhaps intermittent involvement with other members), then you can use a single thread across multiple shifts in story; all Updates pertaining to your character will be posted in that thread. If, however, you are participating in this saga with a group of persons, and that group becomes significantly shattered during the story (such as, say, half of the group being captured and carry away), then a new thread must be created to indicate that shift.
All threads must be of the following form: '[Planet Name] Topic Name'
Thus, suppose you wanted to name your topic 'Excelsior,' and you were participating in the saga on Namek. Your thread would then be titled '[Namek] Excelsior.'
This thread will be posted to intermittently to indicate saga-wide information of relevance to the members.
First, freedom. Do what you like. While a main pathway will be provided in the form of straightforward, army-based combat, there are opportunities for creative risk-taking. Acting as a double-agent, assassinating an enemy general, sabotaging another member's Militia endeavors, etc.; the world is literally open to you.
Second, other-ness. The Chubbs universe is not merely a reflection of your characters, but involves dangers and wills external to your charaters'. This world is dangerous and chaotic, doubly so in a time of intergalactic warfare. The planets spin on, whether you observe it or not.
Saga Structure
Of course, not all endeavors will succeed. Ambitious aims will require ambitious (and consistent) roleplaying.
To reflect the malleability of the story, and the impact of the individual characters, the saga will consist of a series of four-day cycles. For the entirety of the first three days of a cycle, as well as the fourth day (up to 6 PM EST), roleplaying may occur. But, on the fourth day, after 6 PM EST, the saga will be temporarily closed (this will be referred to as a 'Closure'). During this period, the saga architects (which includes myself, Vad, and Kaden) will update every thread currently active in the saga. Sometimes these updates will be substantial, such as the resolution of a fight, or an evaluation of a particularly significant endeavor. Sometimes these updates will be without substance: 'the battle rages on.' If you make waves, you can expect more substantial updates.
Closures will be scheduled regularly (with a definitive calendar set up shortly). These Closures may take up to, but will take no longer than, midnight. of the same day.
Because of the nature of Closures and Updates, roleplays during the Closure period run the risk of being negated by Updates. If a roleplay is negated (that is, the roleplay contains material rendered illogical or irrational, such as referencing the actions of a character killed off in the Update), then that roleplay will be deleted (after giving the member a chance to save it, in case portions of it can be salvaged). This will be relatively uncommon, but it is nevertheless something to consider. Do not plan out your roleplays too far in advance, particularly if involved in a chaotic environment (such as defending a besieged spaceport); anything can happen, and plans can go awry.
Further, during an Update, there will be multiple buffs and debuffs. All of these will have at least some effect upon your endeavors. For example, if you shoot for an ambitious goal, and meet that goal, you will likely gain a buff (such as increased morale for any troops following you, or increased combat prowess for a short time due to recent victories). If, however, you shoot for an ambitious goal and do not roleplay accordingly, you will likely gain a debuff (such as a broken arm in a combat situation, or decreased troop morale). These will be catalogued and updated in a dedicated topic in the Invasion Discussion sub-forum, organized by member.
Because of the specificity and regularity of Updates, it is important that all saga threads are organized correctly. To this end, consistency of location for members involved in a particular storyline is all important. If you are participating in this saga alone (with perhaps intermittent involvement with other members), then you can use a single thread across multiple shifts in story; all Updates pertaining to your character will be posted in that thread. If, however, you are participating in this saga with a group of persons, and that group becomes significantly shattered during the story (such as, say, half of the group being captured and carry away), then a new thread must be created to indicate that shift.
All threads must be of the following form: '[Planet Name] Topic Name'
Thus, suppose you wanted to name your topic 'Excelsior,' and you were participating in the saga on Namek. Your thread would then be titled '[Namek] Excelsior.'
This thread will be posted to intermittently to indicate saga-wide information of relevance to the members.