Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf 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 Nest
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, OSR, & D&D Variants
*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!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
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, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
NOW LIVE! Today's the day you meet your new best friend. You don’t have to leave Wolfy behind... In 'Pets & Sidekicks' your companions level up with you!
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: 3092497" data-attributes="member: 17691"><p><span style="color: Gray">OOC: Unfortunately DRK-1X may not have the luxury of waiting until after its mission to get answers as to how the nanobots function; it may need that information much sooner.</span></p><p></p><p>DRK-1X's emotive node registers frustration upon learning that it's slicing attempt has been detected. The probot knew that its entry into the central hub's computer network might eventually be noted by the network monitoring droids, but 1X had hoped to obfuscate its physical whereabouts before its access point could be identified. Unfortunately, the environmental changes in its office demonstrated that they'd pin-pointed the droid's location all without 1X even becoming aware that it had been discovered. DRK-1X also hadn't yet managed to pinpoint its Mistress' position, its primary goal. Those failures stung DRK-1X's pride, but the probot didn't have time to dwell on them at the moment.</p><p></p><p>The black spherical probe droid quickly withdraws its Code from the computer network nearly at the speed of light, erasing or modifying access logs as it hastily retreats through the system. Although too late to hide its unauthorized access, 1X could at least hope to leave no further clues in the computer network which might help the empire to identify it or its trail. When complete, the probot disconnects, retracts and stows its scomplink probe. Before heading back to the ventilation grate DRK-1X first stops at the door to tap its control panel to leave the entry open behind it. Hopefully that small action would help to lead its pursuers astray.</p><p></p><p>The probot then turns and re-enters the ventilation shaft and uses its hydrospanner to replace the bolts before turning and racing away through the duct work. The probot only slows down to turn corners before speeding up again as it tries to put as much distance as possible between it and the office it had been in only moments ago. DRK-1X backtracks through previously explored ventilation ducts during its retreat, choosing to make a safe escape rather than penetrating deeper into the central hub for the moment. Once it has covered sufficient ground to hopefully outdistance any pursuit DRK-1X turns and, settling on an alternate route through the ventilation system, resumes it course towards its mistress' assumed location in the main control center.</p><p></p><p><span style="color: Gray">OOC: Assuming it's evaded pursuit, 1X will resume its careful but steady advance through the hub's ventilation ducts and utility shafts. Although it doesn't know Dofina's exact location, traveling towards the main control center should keep 1X busy for a fair bit; I imagine it remains many kilometers away still. Along the way, 1X will refrain from accessing the computer network as much as it might like since it seems to be much more of a risk in the carefully monitored central hub.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">As it travels, 1X hopes to gain covert entry to one of the nearly forty smaller hangar bays. Ideally 1X would pick one that's on its route and perhaps in an incomplete or disused part of the station, with little foot traffic, a few personal shuttles and maintenance droids if at all possible.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">DRK-1X has another plan it wishes to execute while traveling towards the main control center. To that end, 1X will stop in what it considers a relatively safe spot, shut-down momentarily and reprogram itself with the maximum number of ranks and feats in its demolition skill. The probot will then use its new skill along with the data its gained concerning the station's power distribution grid to extrapolate the best spots to position its permacrete detonators for maximum destructive potential</span> <span style="color: LightBlue">(Demolition +17)</span><span style="color: Gray">. DRK-1X is of course hoping to start a chain reaction, but if such explosions aren't as easy to achieve as they are in the movies then 1X will take what it can get. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink ;)" data-smilie="2"data-shortname=";)" /> Once it has chosen five such locations as well as a series of alternate choices that it believes it could reach while en route 1X will shut down once more and reprogram itself back to its former skill-set.</span></p><p><span style="color: Gray"></span></p><p><span style="color: Gray">Detours are acceptable to reach these secondary objectives as long as they don't lead the probot into overly dangerous areas. Taking a circuitous route to reach the main control center might help 1X to avoid drawing attention to its true objective in case security personnel try to track it.</span></p></blockquote><p></p>
[QUOTE="Ambrus, post: 3092497, member: 17691"] [COLOR=Gray]OOC: Unfortunately DRK-1X may not have the luxury of waiting until after its mission to get answers as to how the nanobots function; it may need that information much sooner.[/COLOR] DRK-1X's emotive node registers frustration upon learning that it's slicing attempt has been detected. The probot knew that its entry into the central hub's computer network might eventually be noted by the network monitoring droids, but 1X had hoped to obfuscate its physical whereabouts before its access point could be identified. Unfortunately, the environmental changes in its office demonstrated that they'd pin-pointed the droid's location all without 1X even becoming aware that it had been discovered. DRK-1X also hadn't yet managed to pinpoint its Mistress' position, its primary goal. Those failures stung DRK-1X's pride, but the probot didn't have time to dwell on them at the moment. The black spherical probe droid quickly withdraws its Code from the computer network nearly at the speed of light, erasing or modifying access logs as it hastily retreats through the system. Although too late to hide its unauthorized access, 1X could at least hope to leave no further clues in the computer network which might help the empire to identify it or its trail. When complete, the probot disconnects, retracts and stows its scomplink probe. Before heading back to the ventilation grate DRK-1X first stops at the door to tap its control panel to leave the entry open behind it. Hopefully that small action would help to lead its pursuers astray. The probot then turns and re-enters the ventilation shaft and uses its hydrospanner to replace the bolts before turning and racing away through the duct work. The probot only slows down to turn corners before speeding up again as it tries to put as much distance as possible between it and the office it had been in only moments ago. DRK-1X backtracks through previously explored ventilation ducts during its retreat, choosing to make a safe escape rather than penetrating deeper into the central hub for the moment. Once it has covered sufficient ground to hopefully outdistance any pursuit DRK-1X turns and, settling on an alternate route through the ventilation system, resumes it course towards its mistress' assumed location in the main control center. [COLOR=Gray]OOC: Assuming it's evaded pursuit, 1X will resume its careful but steady advance through the hub's ventilation ducts and utility shafts. Although it doesn't know Dofina's exact location, traveling towards the main control center should keep 1X busy for a fair bit; I imagine it remains many kilometers away still. Along the way, 1X will refrain from accessing the computer network as much as it might like since it seems to be much more of a risk in the carefully monitored central hub. As it travels, 1X hopes to gain covert entry to one of the nearly forty smaller hangar bays. Ideally 1X would pick one that's on its route and perhaps in an incomplete or disused part of the station, with little foot traffic, a few personal shuttles and maintenance droids if at all possible. DRK-1X has another plan it wishes to execute while traveling towards the main control center. To that end, 1X will stop in what it considers a relatively safe spot, shut-down momentarily and reprogram itself with the maximum number of ranks and feats in its demolition skill. The probot will then use its new skill along with the data its gained concerning the station's power distribution grid to extrapolate the best spots to position its permacrete detonators for maximum destructive potential[/COLOR] [COLOR=LightBlue](Demolition +17)[/COLOR][COLOR=Gray]. DRK-1X is of course hoping to start a chain reaction, but if such explosions aren't as easy to achieve as they are in the movies then 1X will take what it can get. ;) Once it has chosen five such locations as well as a series of alternate choices that it believes it could reach while en route 1X will shut down once more and reprogram itself back to its former skill-set. Detours are acceptable to reach these secondary objectives as long as they don't lead the probot into overly dangerous areas. Taking a circuitous route to reach the main control center might help 1X to avoid drawing attention to its true objective in case security personnel try to track it.[/COLOR] [/QUOTE]
Insert quotes…
Verification
Post reply
Community
Playing the Game
Play by Post
Star Wars - DRK-1X and its Mistress
Top