Quoted By:
In case those drones are too slippery, we might have an alternative pathway. The drone network has been finnnicky for days. The cause is obvious now, a slow insertion mesh-attack! The network specs aren't executing properly because all the new code and commands is gumming up the works. It might be possible to broad-link to the entire house network and issue new commands to every drone on it.
You'd need to link in manually to the house tech controls and then build up as much CONTROL as you can (eg: hits using available pools). At the end of the phase, the CONTROL executes if it's not contested and brought back down under managable levels by hostile operators.
Conveniently, the training manual states that one control is roughly equal to one alacrity, which should let you implement a major action insert with no more than 3 control and then that gets broadsent to the entire drone network through the console. Unfortunately, it's very likely that whoever tampered with the systems will notice a broad-based redirect like that and counteract it. So 3 control might not be enough, since they'll likely burn off a bunch!
Finally, less drones active should assist us in overrunning the on-board routines of any remaining. Given Agent Herbies clean bill of health, we can use him as a model for propagating a new workflow. Sorry that got technical, basically, the more of the drones you disable now, the easier it'll be to take control over the rest. Which also means if you don't disable any it'll be harder!!
Isn't tech support fun?
