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

[lucetimods]

Here's some more insight into making another option after reading through some of the discussion. Just to put some of the stuff into perspective.

ICly, the characters are hinging a lot on this diversion. Although we have worked the mission into them succeeding at the sabotage either way, that's because none of us are actually smart enough to write a convincing piece of code to show that. So a big gamble on success? Not their best option.

Option A is attractive because it provides them with the most chance of success. The more they divide their forces, the less effective the sabotage can be, right? Option A is rather nice because two or three people can handle laying the explosives. Sure, people die... but they'll come back later.

Option B is also attractive because it's easy to do. Is it a throw away option? Not really. It may not have any 'bonuses' to it, but the diversion isn't the point of the mission - the droids are. It's the 'sensible' option for the unambitious.

Option C is a risky move that puts the entire mission in danger and may result in them losing their chance at accomplishing anything - at least, this should be their IC mindset. But it also is like effectively doubling what they gain from this mission. It's a gamble. Do you fold now and take your earnings or do you throw in everything and try to win big?

Option D? Well, that's up to you guys. Just remember that the goal is the sabotage. If they put a lot of their people on the job of diversion, then the sabotage is going to be less effective (or ICly they'd be risking failure). There's also keeping the integrity of the mission in tact. How much is too much before they risk blowing their cover? Who can they trust? The Malnosso are an intelligent bunch. How much are they monitoring not just in their base, but above it as well? What kind of tactics might they be using to keep their base safe?

The important thing to remember is that even if its hard-written into the mission they'll succeed at the sabotage, none of them have any idea if they'll even get past the first door safely. So they should plan accordingly.

[touchofrogue]

This is definitely some useful perspective. Hmm.... now I will have to think more.

Still no option A for Rogue, but "B" is now more appealing...

Response to this starting with the bold...

[endgames]

Just a couple notes here - firstly reminding anyone who actually wants their character to be part of the distraction to go down here or make a note of such in response to this comment.

The mod comment about not being able to risk too many people on this reminded me so far I only have an official count of two (maybe three as I'm guessing Leonhardt is going). Most people voting on the plan are saying they're going with the security team, so as of now I don't think they have too many people.

Re: Option D, I just wanted to clarify that nothing about it is deadset aside from making a B-like distraction. As Daisy's mun quoted: "The key to strategy...is not to choose a path to victory, but to choose so that all paths lead to a victory." Shikamaru himself is an example of making sure your back-up plans have back-up plans.

So really, the rest depends on variables. Working with the FTSA? Makes good cover (and since almost every safe option screws them over, might as well give them a chance to really be responsible). Whether it happens or not would depend on the first approach though. If they're suspicious, or risk blowing the cover, it's a no and they do things themselves.

Kidnapping the bureaucrat? Depends on the risk assessment, but the decision is made at the moment. If there's too much risk involved (which could be decided by RNG, both before and halfway through if started), they abandon it.

TL;DR: As complicated as it sounds it's designed to minimalize, and to flow together.

[daisy023]

I wonder if this procedure could go like this -- feel free to correct me or post another if there's something better.

1. Both teams get in position, synchronize watches, and appoint times for events. A-Team sets its sights on Kidston. B-Team sets their own on the bureaucrat.

2. B-Team pulls off the B-kind of distraction. (Fire alarm, stink bomb, bomb threat, etc)

3. A-Team moves in ASAP. First target to neutralize is Kidston, who is rendered unconscious via tranq. darts and stuffed into a box or transported in some manner.

4. B-Team moves in to try to capture the bureaucrat amidst the chaos, possibly with a secondary team. Going to get a lot of attention.

5. A-Team infiltrates the base, gets to work on the sabotage of both programming and assembly. Immediately after the work is done, they have to leave ASAP before the Malnosso search for intruders. Kidston is moved someplace hidden just as well, away from the assembly line that could arouse suspicions.

6. B-Team gathers intel from the bureaucrat, perhaps getting in contact with the FSTA? After A-Team finishes their job, so will theirs.

7. Both teams exit their respective facilities and move to the extraction zone. Preferably with scouts ahead in case the Malnosso are on their trails.

[endgames]

Well the B Team plot I had outlined like so, in a different order.

Aside from that, I agree it will work best if both teams are synchronized. While A Team is getting a start on their part of the plan, the B Team can be blending in with the con and testing the FTSA. After that, it should flow smooth?