Mission Update!

[lucetimods]

Droid Sabotage - Begins September 21st (fyi: we pushed the date up by one!)
Field Leader: Steve Rogers; Security: Alia Shepard, Sophie, Rogue, Greg Lestrade, Gai Tsutsugami, Masaomi Kida, Leonhardt; Stealth: Trafalgar Law, Fujiko Mine, Nara Shikamaru, Albert Silverberg, Loki; Technicians: Donatello, Artemis Fowl II, Daisy, Tony Stark; Programmers: Robert Hastings, Pascal, Doctor “Eggman” Robotnik, Raine Sage

New mission will come later this month! We're going to try out a shorter sign-up time to see if it raises more volunteers.

If you're new here, then this is a mission post. You can find available missions at rpmanager. You are welcome to subscribe or track the journal, but this is not required, as updates will be posted on this journal. For those of you who don't know about missions, the links below should help you out. I suggest you start with the Mission FAQ first!

The log is going up for this current mission at the same time. Check out the details inside for a special chance for one character to play ‘hero’ and save the day. However playing hero doesn’t come cheap, either. There will be a thread on here to volunteer for this role!

OOC: Mission Suggestions | Mission FAQ | Nitpicker's Guide: In-Depth Information | Mission Tracking
IC: Malnosso Information Post | Recurring Missions | Unique Missions | CJ's Announcement

Feel free to discuss and ask questions here! You may use this as a plotting post for the upcoming mission(s) as well.

Comments

MOD QUESTIONS

[lucetimods]

VOTING

[lucetimods]

Participants have three diversion tactic options. Plot elsewhere on this post and then vote here!

The participants will need to organize themselves into teams. While one group intends to escort the technicians and programmers to where their work can be completed in the core code room and assembly line, another group will be responsible for choosing and carrying out a secondary objective that will serve as a distraction tactic. There are three options:

Destroy Resort - 90% success chance
Pros: Cripple facility by drawing attention to it, effective and quick
Cons: Cost of innocent lives, frames the FTSA as terrorists

Ruin or Disrupt Enclosure-Con - 80% success chance
Pros: Easy, accessible, non-violent.
Cons: Nothing gained, further villainizes and marginalizes the efforts of the FTSA, could take considerable time.

Kidnap Bureaucrat - 50% success chance
Pros: Cripple organization with ransom, obtain information, keeps all activity out of the public eye.
Cons: Very dangerous, jeopardizes mission, time-consuming.

[promisebythetree]

Are there really only three options? What if the diversion team got into contact with the FTSA people to arrange a distraction that way?

[the_tv_is_a_lie]

Sticking this up here for Shepard. Work with me here, guys. If there's anything you want her to deal with, just suggest stuff. |D

Security

[touchofrogue]

For... security folks shenanigans? Idk.

Distraction Team

[endgames]

For Plot B, aka the distraction option, I'm still undecided on what's the best pick, but I was curious as to who was planning to stick their character on this team too.

So sound off? I think this is something Shikamaru would put himself on.

Science Team?

[castbytheglyph]

Sup Team A. We might not get to screw around with bomb threats and fire alarms, but we do get the chance to either force down the code room doors or subdue chief programmer 'i'll mutilate my own wings to stop you getting in' Kidston. And of course playing around with the droids too. Fun stuff! Correct me if I get anything wrong from giving all the info a once-over.

Subduing Kidston seems like a good way to go, especially as there are disguise experts kicking around that might be able to take her place in case security starts wondering where the chief programmer suddenly ran off to. I'm still thinking it over, though blowing door seems unfavourable, even if it would free up manpower by not having to worry about keeping an eye on Kidston and all the techies and programmers.

Also, programmer/techie shenanigans? This would probably be the worst possible time to forget about that one missing semicolon.

[touchofrogue]

And here is a plotting thread for Rogue, in case anyone wants to hit me up with individual plotting things?

[chikaidestroyer]

Still not all that sure where I want Albert to go, but he's available for plotting. Getting to know fellow mission-goers. All that good stuff.

He'd be all for ensuring the primary objective (sabotaging the droids) succeeds. He'd be disinclined to take a huge gamble (option C) that could compromise the primary goal of the mission and, you know, lead to their own deaths or captures.

[alloys]

HELLO AND WELCOME TO DROIDBUSTERS

So Tony's a technician and therefore Team A. He'll be sans suit. And he'll be very watchful because of Loki being around, while attempting to glean every single thing he can about droid construction. Tensions gonna run high. So yeah. Plot with me!

FINALIZING SOME THINGS

[endgames]

So I put this in my vote up there, but here is the distraction plan as I see it? Charles was kind enough to make a flow chart, so it should read much simpler as so:



Thoughts, comments, concerns? Cookies?

Also looking for some finalization on who's going to be Team B. The way I have it outlined, all scenarios can be carried out by four people or less (may adjust if one more person really wants in). More than that and it's not just a security risk to the distraction plan, but it's a big one to the Science Team who will need the most people.

AS OF NOW the roster I have from the last time I asked for a headcount is:

- Shikamaru
- Masaomi
- Gai
- Leonhardt (??? Nadia, your comments made me feel you wanted him in but if I'm mistaken let me know)

And yup, that's about it. Carry on. 8|a

[neversurrender]

/CRASHES IN LATE FOR EVERYTHING

So Steve is here for all your plotting needs. He's going to be on Team A and doing team leader things. and for the sake of blending in he'll be without uniform and shield because...yeah. Bring me all the plots!

Final Assignments

[neversurrender]

Comment here with your character + their assigned team. This is just an organization thread to get an idea of where everyone will be.

Team A plan?

[daisy023]

Let's see... For the main plan:

1. Team A waits for the distraction, and have their sights on Kidston if possible. Team B is imposed a time limit to perform their diversion. Just in case, should both teams have a radio operator in an encrypted channel to inform when the diversion is on?

- On one hand, it could simply be a click of their comm channels twice to begin their Op, three if something goes wrong.

1a. If something goes wrong with the distraction, Team A will probably have to enter by force on both the installation and assembly line. When this happens, it goes to point 3cd.

- On another, perhaps simply seeing what happens back in their location could be better. Using radios could be a little risky if the Malnosso catch the frequency, even if the teams are using an encrypted channel.

2. Kidston is neutralized, preferably by tranquilizer darts, unless Loki sods something up and he only uses her wings, or the team is forced to reprogram the wing scanner.

2a. If Kidston is rendered unconscious but alive, she could be stuffed into a crate or closet as they move in to the assembly line.

2b. If Kidston is killed, Loki would be pretending to be her, though... he'd probably risk being left in some location until he escapes by his own means.

(Of minor note, Daisy... wouldn't be too troubled by the death of one of the scientists, given they're part of the enemy. Superior officers, squadmates, civilians, threats, and all that. She just thinks keeping Kidston unconscious would be better in case there are more safety locks needing her alive in some manner.)

2c. If the situation turns far too difficult to deal with either capture or execution of Kidston, the team would be focused on cracking the wing scanner.

2d. Daisy is against this, but if all else fails, they'd put explosives on the door, and perform their task with an extremely low amount of time.

3abc. In the assembly line, the more important sabotages would consist in lightly tampering with the perpetual battery so it stops being one, weakening the joints and the alloy (reducing the carbon density), and programmers could disable a number of reactions, or even just introducing a handful of lines that could make it prone to glitch sometimes.

Preferably, only the more basic tasks could be done, both for time and subtlety in the droids' defects.

(A few suggestions: in programming? Disabling a line is less dangerous than deleting it. And patches in software are called that, because they're put over the original program to correct things. Even a single wrong line of code could have repercussions on the operation of the droids.)

3cd. With the attention forcing the door open might cause, or the lack of time, Team A would make only the most basic forms of sabotage in the assembly: Battery tampering, slight alloy changing, and a handful of lines of code.

4. Team A escapes the facility, preferably evading the sight of everyone, sets a scout ahead in case they are being followed, and reaches the extraction point.