Difference between revisions of "Boardroom Bloodbath"
(Created page with "==Player AARs== ===John===") |
(→John) |
||
| Line 1: | Line 1: | ||
==Player AARs== | ==Player AARs== | ||
===John=== | ===John=== | ||
''Record Date: 1-20-2079 '' | |||
''Record Tags: [Shadowrun], [Oztech], [Wetwork]'' | |||
''First run in conjunction with the Haven organization Ellie put me in contact with. The Johnson was apparently a repeat customer with the organization, and he seemed to have some regard for the team. Job was a hit on eight high-level execs at Oztech Systems, and the J supplied a time and place where the targets were known to be meeting. The room was heavy on protection, and given the number of targets, the plan was to infiltrate and plant a timed explosive. Clean-up and plan B involved turning the room into a shooting gallery from the outside, penetrating reinforced glass. The team's decker never showed (going to have to ask Ellie if the Haven is known for that), so we needed a solution for matrix threats. Team decided to take care of the site's spider the night before the hit, which went off smoothly. I assumed the identity of the spider (note: SIN and ID cards are attached to this report, but target is currently incarcerated and the IDs deactivated. Possible use as a decoy or red herring later.) and entered the facility using his identity. The bomb was magical, courtesy the team's alchemist, and the lynchpin a small needle. The plant went off cleanly, but a third-party bug was discovered in the room. (Note: bug is cataloged in secure storage, schedule a follow-up investigation). The external security team brought to the meeting was ineffective at detecting the lynchpin, and the subsequent explosion succeeded in eliminating 7/8 of the targets. Plan B was executed immediately, and a fire elemental completed the job. The payout went cleanly, though only the Johnson's personal security showed.'' | |||
''Action: The responsible party for the bug is currently unknown. Lead should be followed in case the Johnson is involved or Haven has an active secondary threat.'' | |||
''Action: The run has been recorded and cataloged. The Johnson is sensitive to this data and will react negatively to its release. Footage archived for leverage in case of trouble.'' | |||
Revision as of 22:38, 25 January 2018
Player AARs
John
Record Date: 1-20-2079
Record Tags: [Shadowrun], [Oztech], [Wetwork]
First run in conjunction with the Haven organization Ellie put me in contact with. The Johnson was apparently a repeat customer with the organization, and he seemed to have some regard for the team. Job was a hit on eight high-level execs at Oztech Systems, and the J supplied a time and place where the targets were known to be meeting. The room was heavy on protection, and given the number of targets, the plan was to infiltrate and plant a timed explosive. Clean-up and plan B involved turning the room into a shooting gallery from the outside, penetrating reinforced glass. The team's decker never showed (going to have to ask Ellie if the Haven is known for that), so we needed a solution for matrix threats. Team decided to take care of the site's spider the night before the hit, which went off smoothly. I assumed the identity of the spider (note: SIN and ID cards are attached to this report, but target is currently incarcerated and the IDs deactivated. Possible use as a decoy or red herring later.) and entered the facility using his identity. The bomb was magical, courtesy the team's alchemist, and the lynchpin a small needle. The plant went off cleanly, but a third-party bug was discovered in the room. (Note: bug is cataloged in secure storage, schedule a follow-up investigation). The external security team brought to the meeting was ineffective at detecting the lynchpin, and the subsequent explosion succeeded in eliminating 7/8 of the targets. Plan B was executed immediately, and a fire elemental completed the job. The payout went cleanly, though only the Johnson's personal security showed.
Action: The responsible party for the bug is currently unknown. Lead should be followed in case the Johnson is involved or Haven has an active secondary threat.
Action: The run has been recorded and cataloged. The Johnson is sensitive to this data and will react negatively to its release. Footage archived for leverage in case of trouble.