cold calculations

The targeting program on the blockading trade federation ship targeting the fleeing Naboo Vessel was programmed to be cost effective, it was also programmed to follow its orders, and way down the priority chain near the bottom added on in the final stages of its creation was the ability to interpret its orders. The order of how it was created and their priorities to each other most often did not make a difference, but sometimes it did. In this case the blockading ship had standing orders to conduct all things cost efficiently, enforce the blockade, no ships to exit, there was also the new order to disable the lone ship exiting atmosphere for capture.

The targeting program started off with long range turbo laser bombardment, this seemed to work as the shields on the approaching vessel failed, the program then switched over to precision mode to finish disabling the craft. The sensors picked up movement on the surface of the Naboo craft as astrodroids swarmed over the damaged area in an attempt to repair the ship. The program calculated the projected damage verses the number of astrodroids and came up with a result that the ship would likely be able to get past if they could get repaired. This number barely climbed higher then the threshold of cost efficiency and the program sent an order to one of the ships missile launchers and a moment later a lone missile raced towards the approaching ship.

The missile did its job and more, destroying the droids, and causing the back end of the ship to break off cutting the power to the long front section of the ship. The Naboo ship was now disabled, with surprisingly low casualties with only one figure on its sensors being flung from the now slowly tumbling ship, a quick zoom quickly identified the figure as a Gungan, a native of the planet below. Its task now complete the targeting program went into low power mode, not once questioning why a gungan would be on the ship in the first place.