▶ RETURN TO HARBOUR
The anniversary of Neo's Truce is among the few annual events that mark the turning of the long, dark years, and is undoubtedly the most exuberant of them all, lasting up to a week of festivities. This particular anniversary will be marked by a specific event -- the unveiling of a new hovercraft prototype that promises to usher in a new era of technological advancement for the fleet.
However, on the second day, the celebrations are cut short when a hovercraft returns from what was a simple scouting mission with news that Sentinels attacked and destroyed four ships, a massive blow to the Zion Defense Grid.
Starting March 1, the first two weeks of our game will be dedicated to coordinated investigations to uncover the extent of the emergency and locate its source to find out what happened and hopefully instigate a rescue. While response is immediate, it is also ongoing, requiring for people both familiar and unfamiliar with one another to band together.
▼ CONSOLIDATION
Although we do not yet have full crews, Return to Harbour requires at least two skeleton crews of player characters to man hoverships, and we will accept more if interest is high enough, with a minimum of five people per ship.
By order of the Council, two captains have been instated for the duration of this mission: Simon Metzger of the Nidhoggr and Wedge Antilles of the Durga. Though these crews may be temporary or “on contingency,” it will nonetheless be a good opportunity to mix and match, test out roles both current and prospective, and perhaps form new alliances for future permanent or semi-permanent crewmanship.
Regarding specific shipboard positions, we would like to make say that characters should feel free to take dual roles or even 'moonlight' different roles, especially in light of our current operator shortage (e.g., operator/engineer, operator/operative) -- while being an operator requires code fluency, it is also a priority learned skill for those who have been on ships for some time and is particularly obtainable by tech-savvy characters. Remember, having a wide ranging experience in running the ship makes you an invaluable asset (within the parameters of your established and developing skillset, of course). Taking up positions for this plot will not prevent you from future changes. You can always agree to one or two months before moving on and needing replacement, allowing for high turn over and mingling CR.
Taken together with your CR Meme responses, we recommend you use this post for sign-ups and feel free to also briefly discuss team dynamics. Although of course we encourage you to RP whatever you want, we strongly recommend you focus on (or check that others have already) getting the follow essential roles filled:
Pilot
Operator (may be dual/moonlighting role)
Operative (may be dual/moonlighting role)
Again, these crews may be temporary. However, those with a substantial roster of fully committed players will eventually be finalized on the Recruitment page.
Much about this plot will be determined by who signs up! However, please also be aware that staying home in Zion will carry equally important opportunities. Politics in Zion will become a hotbed of conflict that may warrant investigation or even jeopardize the dispatched crews, analyses may be done in home computers, and the Oracle herself might have something to say about the events that have transpired.
▼ VOLUNTEERS
In addition to the above teams and ensuing mission, we need TWO volunteers. These volunteers must have the capacity to pilot, operate, or at least conduct rudimentary communications monitoring, which would be a standard crew skill. You must also have the capacity to be RPable starting March 1. Volunteering will not exclude you from the above activities, but will assist us in some plot delivery. The named captains cannot volunteer.
Please comment here to volunteer. If more than two people sign up, we will randomly select participants lottery-style, who will be chosen on March 1.