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
Upgrade your account to a Community Supporter account and remove most of the site ads.
Enchanted Trinkets Complete--a hardcover book containing over 500 magic items for your D&D games!
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: 2987188" data-attributes="member: 17691"><p>[sblock=OOC]<span style="color: Gray">Darn. I was hoping it would be a maintenance droid rather than an organic technician. That would have proven easier to deal with I think. Gee. I've been mulling over what to do all day; it certainly wasn't an easy call. 1X will just cross its fingers and hope it chose wisely. <img src="http://www.enworld.org/forum/images/smilies/paranoid.png" class="smilie" loading="lazy" alt=":uhoh:" title="Paranoid :uhoh:" data-shortname=":uhoh:" /> </span>[/sblock]Emitting the electrostatic pulse buys the concealed probot a few more precious seconds for its heuristic processor to work its way through its carefully refined improvisational problem solving algorithms. DRK-1X's targeting sensors lock onto the male as he pulls his hand away from his comlink and rises to step towards the wall panel. Millisecond by millisecond, trillions of electrons race through the droid's processor circuit pathways as it compares possible scenarios, their probable outcomes, and which would best serve its long term goal of reaching its Mistress.</p><p></p><p>Should the man be allowed to report the saboteur's death and summon help or should he be silenced immediately with a well targeted blaster bolt? Which outcome presented the greatest risk of detection and capture? Subduing the man would most likely keep the probot from being detected in the short term, but the technician would most likely be called upon or missed at some point during the upcoming hyperspace trip. DRK-1X could possibly perform the man's duties for a time to keep anyone from noticing his inactivity, but it seemed unlikely that the probot could avoid interacting with the crew completely for the several days the trip would last. If the technician were allowed to summon help others would likely arrive to investigate the body, its murder and the sabotage of the hub's systems. A close study of the scene would reveal the murderer's handprints around the body's neck along with his fingerprints and organic residue on the panels, components and the ventilation shaft leading out. Investigators would correctly conclude that an organic was responsible for the murder and sabotage; they wouldn't likely suspect or search the ship for a small probot left aboard. Considering the pressing schedule the freighter was expected to maintain, it was even possible that no official investigation could be organized and carried out before the freighter lifted off. DRK-1X could potentially remain aboard undetected...</p><p></p><p>Its heuristic processor having reached its volition threshold, DRK-1X watches the man as he crosses the small cabin and depresses the wall panel's comlink button. Trusting that the technician was sufficiently unnerved by the discovery of the murder and distracted by his comlink conversation, 1X slowly rises from its concealed position and silently floats forward. The probot carefully deploys its second manipulator arm and, coming to a stop before the six stacked permacrete detonators, cautiously begins gathering up the explosives while attempting to remain undetected <span style="color: LightBlue">(Hide +22, Move Silently +15, taking 10)</span>. Without wasting another moment, DRK-1X turns and silently floats through the hatchway from which the technician had emerged a moment ago. Heading aft, the black spherical probot makes its way cautiously towards the closest of the two storage bays.</p></blockquote><p></p>
[QUOTE="Ambrus, post: 2987188, member: 17691"] [sblock=OOC][COLOR=Gray]Darn. I was hoping it would be a maintenance droid rather than an organic technician. That would have proven easier to deal with I think. Gee. I've been mulling over what to do all day; it certainly wasn't an easy call. 1X will just cross its fingers and hope it chose wisely. :uhoh: [/COLOR][/sblock]Emitting the electrostatic pulse buys the concealed probot a few more precious seconds for its heuristic processor to work its way through its carefully refined improvisational problem solving algorithms. DRK-1X's targeting sensors lock onto the male as he pulls his hand away from his comlink and rises to step towards the wall panel. Millisecond by millisecond, trillions of electrons race through the droid's processor circuit pathways as it compares possible scenarios, their probable outcomes, and which would best serve its long term goal of reaching its Mistress. Should the man be allowed to report the saboteur's death and summon help or should he be silenced immediately with a well targeted blaster bolt? Which outcome presented the greatest risk of detection and capture? Subduing the man would most likely keep the probot from being detected in the short term, but the technician would most likely be called upon or missed at some point during the upcoming hyperspace trip. DRK-1X could possibly perform the man's duties for a time to keep anyone from noticing his inactivity, but it seemed unlikely that the probot could avoid interacting with the crew completely for the several days the trip would last. If the technician were allowed to summon help others would likely arrive to investigate the body, its murder and the sabotage of the hub's systems. A close study of the scene would reveal the murderer's handprints around the body's neck along with his fingerprints and organic residue on the panels, components and the ventilation shaft leading out. Investigators would correctly conclude that an organic was responsible for the murder and sabotage; they wouldn't likely suspect or search the ship for a small probot left aboard. Considering the pressing schedule the freighter was expected to maintain, it was even possible that no official investigation could be organized and carried out before the freighter lifted off. DRK-1X could potentially remain aboard undetected... Its heuristic processor having reached its volition threshold, DRK-1X watches the man as he crosses the small cabin and depresses the wall panel's comlink button. Trusting that the technician was sufficiently unnerved by the discovery of the murder and distracted by his comlink conversation, 1X slowly rises from its concealed position and silently floats forward. The probot carefully deploys its second manipulator arm and, coming to a stop before the six stacked permacrete detonators, cautiously begins gathering up the explosives while attempting to remain undetected [COLOR=LightBlue](Hide +22, Move Silently +15, taking 10)[/COLOR]. Without wasting another moment, DRK-1X turns and silently floats through the hatchway from which the technician had emerged a moment ago. Heading aft, the black spherical probot makes its way cautiously towards the closest of the two storage bays. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
Playing the Game
Play by Post
Star Wars - DRK-1X and its Mistress
Top