Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Next
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
Twitch
YouTube
Facebook (EN Publishing)
Facebook (EN World)
Twitter
Instagram
TikTok
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
The
VOIDRUNNER'S CODEX
is LIVE! Explore new worlds, fight oppressive empires, fend off fearsome aliens, and wield deadly psionics with this comprehensive boxed set expansion for 5E and A5E!
Community
Playing the Game
Play by Post
Star Wars - DRK-1X and its Mistress
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Ambrus" data-source="post: 3097837" data-attributes="member: 17691"><p><span style="color: Gray">OOC: DRK-1X has multiple related goals in wanting to plant explosives around the facility. With only six permacrete detonators it'll have to be choosy about where it plants them. It wants to keep at least one with itself as a final option in case it is captured; that leaves five others. 1X plans on leaving one within the habitat section where Dofina is located near the main control center, next to that section's primary power relay would be ideal I think. The goal here is to utterly annihilate its mistress' living and working area so as to leave no clue of her fate once she's left that section. If all else goes well that one will be the last detonator to be set once 1X locates Dofina.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">Assuming that Dofina's habitat section and the flight control station aren't close enough together to be taken out by the single detonator, the second to last detonator will be set in a position to take out that second target. Again, setting it next to that sections' main power relay would be ideal I think. The goal here is to destroy or at least disrupt the flight control station's normal operations so that the imperial forces will have a difficult time tracking and identifying ships around the construction facility, such as the Ari's Sorrow, once 1X and Dofina are ready to escape.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">That leaves three detonators. DRK-1X would ideally like to place two of them in a position to destroy or disable the station's main reactor. Can you give me a better idea of how many detonators would be necessary to cause a full-fledged reactor breach? The goal here is to cause the biggest distraction possible to disrupt all of the imperial forces by throwing them into chaos. Since the main reactor is so big its 1X's hope that the security measures in place will be unable to protect its entire bulk all at once, allowing the probot to exploit some openings here and there. The final detonator 1X wants to hide in or near the shuttle repair bay its found; the purpose being to thoroughly erase any of its handiwork left behind there. Again, planting it next to the nearest power relay would be preferable.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">DRK-1X's plan in setting all the detonators is to reach a hard to access maintenance hatch or out-of-sight cranny somewhere near its targets; ideally behind an innocuous bolted panel where they'll be hard to detect or find in a search. DRK-1X doesn't want to risk all or nothing in trying to set up any particular explosive device however. Hopefully, since the detonators have such a large yield, 1X won't have to risk getting too close to its intended targets. Ideally, placing them nearby will be sufficient to critically damage each target and so cause maximum destruction. Now that it's inside the central hub, 1X isn't too worried about taking its time. With boundless patience, 1X can easily remain in a concealed spot for hours or days if necessary to wait for the perfect moment to covertly reach or leave a targeted location. If it judges that the in-place security measures are too dangerous to risk penetrating then 1X will reconsider its target and choose a secondary spot near a key power relay to place its detonators. To these ends, 1X will plot a route for itself through the central hub to pass by each spot in turn before heading towards Dofina.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">The junkyard nature of the hangar bay that 1X is observing sounds ideal for its needs; piles of junk and many partially disassembled shuttles should provide it with plenty of cover and hiding spots as it stealthily moves around the place. What type of maintenance droids are there in the hangar; treadwells, LE repair droids, R series astromechs?... Hopefully these droids don't possess much in the way of security programming and so won't be suspicious or be particularly alarmed if they see something out of the ordinary going on around them. Once again, stealth and success matter more to 1X at this point than does speed. To that end 1X will take all the time it needs to carefully move around the place, select its targets, avoid the human guards and pick the best opportunities to act, perhaps only acting during guard shifts. 1X's ultimate goal here is to gain control of all the maintenance droids here and, through them, control of the hangar bay and its equipment.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">The probot has multiple goals it wants to achieve while here. First of all, it wants to reduce its chances of raising an alarm while simultaneously securing some aid. To that end 1X will choose a maintenance droid that is in an isolated part of the hangar bay by itself, busily working at its assigned task; one who is alone and out of sight working inside a shuttle would be ideal. DRK-1X will use its stealth abilities to sneak up behind it and, assuming it hasn't been upgraded with locked access, shut it off with a tap to its shutdown switch. 1X will then hurriedly proceed to plug itself into the droid and reprogram it while keeping a keen eye out for anyone else approaching their location. DRK-1X isn't particularly interested in scanning the droid's memories or its programming; all it wants to do is change its ownership and obeisance protocols so that it'll follow 1X's instructions ahead of anyone else's. Assuming it succeeds, 1X will then program the droid with a series of instructions to follow and goals it wants the maintenance droid to covertly pursue while seemingly continuing with its regularly assigned duties. DRK-1X will then reactivate the droid. The maintenance droid's first such task is to assist 1X by keeping a lookout and intercepting and occupying people while the probot approaches, shuts-down and reprograms another droid in a similar fashion; and so on and so on... 1X may also charge a reprogrammed maintenance droid to approach and shut down one of its lot mates rather than risk doing so itself if it seems expedient to do so.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">The next step is to have the droids identify (and repair if necessary) one of the shuttles' com-systems. DRK-1X wants to set it up so that it continuously monitors a set com-channel chosen by 1X so that it will retransmit any encrypted transmissions it receives with its superior range. 1X doesn't want to risk trying to slice one of the stations' com-systems if avoidable; leap-frogging an encrypted signal to the Ari's Sorrow through a derelict shuttle's com-system is a good alternative plan I think.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">The probot's final goal is to covertly enter and pre-program one or more of the shuttles here so that it can operate them remotely via its encrypted comlink. Ideally they'd end up pre-programmed to power up and fly out of the hangar bay on their own and then to travel to a set of transmitted coordinates. DRK-1X could hide aboard one of the shuttles while performing the programming itself and then direct the maintenance droids to ensure that the shuttle is properly prepped, in good working order, fueled and stocked once 1X leaves the hangar bay. The droids could then go about their regular duties while similarly prepping other shuttles along the same lines as the first; even going so far as to copy 1X's special flight programming to the other vessels. Given enough time and luck, the maintenance droids might be able to get a handful of these shuttles ready to fly at 1X's command. If and when 1X sent the activation command the maintenance droids would be ready to manually open the hangar doors, disengage the air shield and generally help to facilitate the shuttle(s) departure.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">BTW, I don't believe you ever told me what was on Four's datastick...</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">I know these plans are far reaching and convoluted but 1X is trying to do everything possible to increase its chances of successfully carrying out its mission; its Mistress deserves no less. Feel free to adjudicate all this however you see fit. We can play through each part or you can summarize the results if you prefer. You've been doing a fine job so far. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> </span></p></blockquote><p></p>
[QUOTE="Ambrus, post: 3097837, member: 17691"] [COLOR=Gray]OOC: DRK-1X has multiple related goals in wanting to plant explosives around the facility. With only six permacrete detonators it'll have to be choosy about where it plants them. It wants to keep at least one with itself as a final option in case it is captured; that leaves five others. 1X plans on leaving one within the habitat section where Dofina is located near the main control center, next to that section's primary power relay would be ideal I think. The goal here is to utterly annihilate its mistress' living and working area so as to leave no clue of her fate once she's left that section. If all else goes well that one will be the last detonator to be set once 1X locates Dofina. Assuming that Dofina's habitat section and the flight control station aren't close enough together to be taken out by the single detonator, the second to last detonator will be set in a position to take out that second target. Again, setting it next to that sections' main power relay would be ideal I think. The goal here is to destroy or at least disrupt the flight control station's normal operations so that the imperial forces will have a difficult time tracking and identifying ships around the construction facility, such as the Ari's Sorrow, once 1X and Dofina are ready to escape. That leaves three detonators. DRK-1X would ideally like to place two of them in a position to destroy or disable the station's main reactor. Can you give me a better idea of how many detonators would be necessary to cause a full-fledged reactor breach? The goal here is to cause the biggest distraction possible to disrupt all of the imperial forces by throwing them into chaos. Since the main reactor is so big its 1X's hope that the security measures in place will be unable to protect its entire bulk all at once, allowing the probot to exploit some openings here and there. The final detonator 1X wants to hide in or near the shuttle repair bay its found; the purpose being to thoroughly erase any of its handiwork left behind there. Again, planting it next to the nearest power relay would be preferable. DRK-1X's plan in setting all the detonators is to reach a hard to access maintenance hatch or out-of-sight cranny somewhere near its targets; ideally behind an innocuous bolted panel where they'll be hard to detect or find in a search. DRK-1X doesn't want to risk all or nothing in trying to set up any particular explosive device however. Hopefully, since the detonators have such a large yield, 1X won't have to risk getting too close to its intended targets. Ideally, placing them nearby will be sufficient to critically damage each target and so cause maximum destruction. Now that it's inside the central hub, 1X isn't too worried about taking its time. With boundless patience, 1X can easily remain in a concealed spot for hours or days if necessary to wait for the perfect moment to covertly reach or leave a targeted location. If it judges that the in-place security measures are too dangerous to risk penetrating then 1X will reconsider its target and choose a secondary spot near a key power relay to place its detonators. To these ends, 1X will plot a route for itself through the central hub to pass by each spot in turn before heading towards Dofina. The junkyard nature of the hangar bay that 1X is observing sounds ideal for its needs; piles of junk and many partially disassembled shuttles should provide it with plenty of cover and hiding spots as it stealthily moves around the place. What type of maintenance droids are there in the hangar; treadwells, LE repair droids, R series astromechs?... Hopefully these droids don't possess much in the way of security programming and so won't be suspicious or be particularly alarmed if they see something out of the ordinary going on around them. Once again, stealth and success matter more to 1X at this point than does speed. To that end 1X will take all the time it needs to carefully move around the place, select its targets, avoid the human guards and pick the best opportunities to act, perhaps only acting during guard shifts. 1X's ultimate goal here is to gain control of all the maintenance droids here and, through them, control of the hangar bay and its equipment. The probot has multiple goals it wants to achieve while here. First of all, it wants to reduce its chances of raising an alarm while simultaneously securing some aid. To that end 1X will choose a maintenance droid that is in an isolated part of the hangar bay by itself, busily working at its assigned task; one who is alone and out of sight working inside a shuttle would be ideal. DRK-1X will use its stealth abilities to sneak up behind it and, assuming it hasn't been upgraded with locked access, shut it off with a tap to its shutdown switch. 1X will then hurriedly proceed to plug itself into the droid and reprogram it while keeping a keen eye out for anyone else approaching their location. DRK-1X isn't particularly interested in scanning the droid's memories or its programming; all it wants to do is change its ownership and obeisance protocols so that it'll follow 1X's instructions ahead of anyone else's. Assuming it succeeds, 1X will then program the droid with a series of instructions to follow and goals it wants the maintenance droid to covertly pursue while seemingly continuing with its regularly assigned duties. DRK-1X will then reactivate the droid. The maintenance droid's first such task is to assist 1X by keeping a lookout and intercepting and occupying people while the probot approaches, shuts-down and reprograms another droid in a similar fashion; and so on and so on... 1X may also charge a reprogrammed maintenance droid to approach and shut down one of its lot mates rather than risk doing so itself if it seems expedient to do so. The next step is to have the droids identify (and repair if necessary) one of the shuttles' com-systems. DRK-1X wants to set it up so that it continuously monitors a set com-channel chosen by 1X so that it will retransmit any encrypted transmissions it receives with its superior range. 1X doesn't want to risk trying to slice one of the stations' com-systems if avoidable; leap-frogging an encrypted signal to the Ari's Sorrow through a derelict shuttle's com-system is a good alternative plan I think. The probot's final goal is to covertly enter and pre-program one or more of the shuttles here so that it can operate them remotely via its encrypted comlink. Ideally they'd end up pre-programmed to power up and fly out of the hangar bay on their own and then to travel to a set of transmitted coordinates. DRK-1X could hide aboard one of the shuttles while performing the programming itself and then direct the maintenance droids to ensure that the shuttle is properly prepped, in good working order, fueled and stocked once 1X leaves the hangar bay. The droids could then go about their regular duties while similarly prepping other shuttles along the same lines as the first; even going so far as to copy 1X's special flight programming to the other vessels. Given enough time and luck, the maintenance droids might be able to get a handful of these shuttles ready to fly at 1X's command. If and when 1X sent the activation command the maintenance droids would be ready to manually open the hangar doors, disengage the air shield and generally help to facilitate the shuttle(s) departure. BTW, I don't believe you ever told me what was on Four's datastick... I know these plans are far reaching and convoluted but 1X is trying to do everything possible to increase its chances of successfully carrying out its mission; its Mistress deserves no less. Feel free to adjudicate all this however you see fit. We can play through each part or you can summarize the results if you prefer. You've been doing a fine job so far. :) [/COLOR] [/QUOTE]
Insert quotes…
Verification
Post reply
Community
Playing the Game
Play by Post
Star Wars - DRK-1X and its Mistress
Top