Privacy Screen

Array Hack Job

Dis-Array

Cover Needed

Array Hack

~mission(MissionLocation) Problem

Lights Out

A couple of ~mission(Client) are working on a big score and they need ~mission(MissionLocation|Address) shut down to make sure they get some privacy. Once it's offline, we'll need you to hang out there to make sure the commlink stays down long enough. ~mission(Danger)\n\nAnd DON'T forget, you'll need a CRYPTOKEY to access the array's controls. \nBring your own if you want, but you can head to ~mission(Location|Address) and grab one there.\nHate for you to head all the way out to the array and not be able to do the damn job.

~mission(MissionLocation|Address) being online's going to be a problem for some ~mission(Client) working the area. \nShut it down, keep it offline 'til the job's complete, and we'll make it worth your while. ~mission(Danger)\n\nOf course, you won't be able to access the array's controls unless you have a CRYPTOKEY with you. \nWe arranged for one to be waiting for you at ~mission(Location|Address) if you don't already have one. 

I don't want to get too specific, but let's just say it would be better for everyone if someone could make sure that ~mission(MissionLocation|Address) was taken out of commission and that it stayed that way for a while. ~mission(Danger)\n\nAnd I shouldn't have to mention this, but for the love of everything, bring a CRYPTOKEY with you. Last thing we need is you showing up unprepared. \nActually, you know what, if you don't already have one, there's a cryptokey at ~mission(Location|Address) that you can use.

Certain ~mission(Client) have a job in the works, but they can't do it as long as the ~mission(MissionLocation|Address) is still online. Need a systems-grok to disable the comm uplink, and stay onsite long enough to make sure there aren't any issues. ~mission(Danger) Credits on completion. No up-front. \n\n---> REMINDER: Bring a CRYPTOKEY with you to hack the array's controls. Either grab one from ~mission(Location|Address) or bring your own.

Here's the breakdown -  ~mission(MissionLocation|Address) needs to be taken offline, and ~mission(Client) are looking to hire a hacker to do it and guarantee the uplink's down for as long as needed. ~mission(Danger)That's about all you need to know.\n\n*** P.S. You'll need a CRYPTOKEY to access the control panel. We arranged one to be waiting for you at ~mission(Location|Address), but if you prefer to use your own, that's fine too.

I wouldn't be surprised if some trouble showed up when all is said and done. 

There are regular patrols of the area, so be ready just in case some unwanted visitors show up. 

I'm not expecting trouble, but knowing what security is like in that sector, it's not out of the question. 

If I'm being honest, these ~mission(Client) had one of their own try to handle the array, and they got taken out. Just don't let the same thing happen to you. Go in prepared, you should come out fine. 

Nine Tails

Dusters

Low Riders

NovaRiders

heavy hitters

people I know

individuals

professionals

< / NOT AVAILABLE / >

PRIVATE SENDER

NOT LISTED

** ERROR **

?????

<= UNINITIALIZED =>

~mission(Item)