<hr/><span class="bbc_u"><br/>Name: Roger O'Hare<br/>Location: Chubs Frigate Cargo Ship at Falaknuma Ship Docks<br/></span><hr/><br/>Roger could tell from the shifting that something was amiss, but had absolutely no idea what was wrong with the pair of hunters. Since they refused to speak to him he guessed they were assenting, but maybe he was shooting himself in the proverbial foot by arming these cannons when the Ohana wanted these creatures...<br/><br/>Unsealing the first radioactive fuel rod, he carefully inserted it in the massive canon stored within hoping he was managing to do it correctly based on the shoulder mounted fuel rod gun he’d once had the pleasure of disassembling, making sure to leave a half twist and the last wire in the circuit undone. With luck the Hunters wouldn't know about the wire, and he should be able to enable the cannon externally if they weren't rampaging when they were freed. Then Roger repeated that process with the second crate, finishing the process with about 15 minutes to spare on his radiation suit. Shimmying out of his suit Roger checked his pad and saw the security alert, but also saw that his pad had isolated itself and turned off all wireless connections per the security software. That would complicate accessing security camera feeds, but Roger was able to use the console in the cargo bay to verify the route was clear and return to his cabin, no one on the ship wiser he'd left. Whoever the hacker was might be able to see him, if they were good enough.<br/><br/><hr/><strong><span class="bbc_u">Name:</span></strong>Dexter<br/><strong><span class="bbc_u">Location:</span></strong>Flood 89 at Falaknuma Ship Docks<hr/><br/>As Dexter's runtimes monitored more camera feeds and compared them to the processes he'd left in the crew files and correlated faces, a name popped up. Roger O'Hare. Curiosity caused the AI to suspend the motoring runtime it had on Roger for about half a second, long enough to access and thoroughly review the file on him in the ships files. Long enough also to notice the clear (to an AI) tampering, though it was the pattern of tampering that was interesting. Things like personal history before joining the UNSC were intact, portions of the UNSC files were tampered with, and almost all of the history post leaving the UNSC. Since the files were 'originals' loaded on the ships systems the tampering had happened earlier, before Roger had joined Chubs. Curiosity caused Dexter to split off a process to Roger's personal storage on the ships systems, and keep watching as Roger entered a crate which the cargo manifest identified as one of the two Ressaw was expecting, with an object that looked suspiciously like a radioactive fuel rod.<br/><br/>An alert from a sub process and a hundredth of a second later Dexter had determined the only files in Roger's personal storage were a map of ordnance placed throughout the ship rigged to explode, the detonation code that was required to do so if an audio receiver failed to pick up a key phrase, and all of Roger's message traffic (which also confirmed Dexter's appraisal that this was the person who'd sent the message). There were a few other pointers to files on a different system, but it seems that a fairly advanced anti-intrusion program had isolated that system, shutting off all it's connections to the ships systems. Leaving a routine to monitor in case the system re-connected Dexter returned to his other processes and watched events continue to play out on this dinky little ship...