FANDOM


"Pull all escort wings in that area off their duty. Send them all against Kanan!"
"Against who, Captain?"
"Renegade One! The guy shooting at everyone!"
―Rae Sloane, to Cauley[src]

Cauley was a human male who served as an Imperial Navy ensign aboard the Imperial Star Destroyer Ultimatum during the Gorse conflict in 11 BBY, in which the Imperial cyborg Count Denetrius Vidian attempted to improve thorilide mining efficiency on the planet Gorse and its moon, Cynda. Shortly after Ultimatum arrived in the Gorse system, Vidian fed the output from Cauley's terminal on Ultimatum's bridge into his optical implants. Unaware of what Vidian was doing, Cauley was at first confused by the count's actions but was soon allowed to return to his work. Later, in the final stages of the conflict, Cauley reported to Ultimatum's captain, Rae Sloane, on the actions of the freighter Moonglow-72 as it tried to prevent Vidian's plan to destroy Cynda from coming to fruition.

BiographyEdit

"I've got a TIE pilot chasing after the hauler he's escorting now. It's fleeing, afraid of being targeted by Renegade One. Our pilot's asking if he can shoot his hauler down."
―Cauley, to Rae Sloane[src]

In 11 BBY,[2] Cauley served in the Imperial Navy as an ensign and tactical officer aboard the Imperial-class Star Destroyer Ultimatum during the vessel's mission to the planet Gorse. Commanded by Captain Rae Sloane, the Star Destroyer's purpose was to transport and serve cyborg Count Denetrius Vidian while he improved the efficiency of thorilide mining on Gorse's moon, Cynda. When Ultimatum first arrived in the Gorse system, Cauley was stationed at a tactical console on the Star Destroyer's bridge, which displayed the locations of all of the other ships in the star system. Immediately after exiting hyperspace, Ultimatum nearly collided with a freighter named Cynda Dreaming, which clipped the larger vessel while narrowly dodging a full on collision. Moments later, Vidian arrived on the bridge and pushed past Cauley to his console, feeding the visual output from the ensign's screen into his optical implants, allowing the count to monitor the nearby vessels and Cauley to return to his work. After thorolide production totals began being transmitted to Ultimatum by the Mining Guild, Vidian moved away from Cauley's station to a data terminal and then ordered that Cynda Dreaming be destroyed after it was discovered that the freighter was delaying the convoy of ships heading from Gorse to Cynda.[1]

Ultimatum

Cauley served as an ensign on board the Ultimatum.

Cauley was present at his station on the bridge when Ultimatum oversaw freighters transporting canisters of the explosive chemical baradium-357 from the Calcoraan Depot space station in the Calcoraan system to the Gorse system. The chemical was to be used to destroy Cynda, allowing the thorilide it contained to be harvested from the debris by Vidian's vessel Forager. However, a group of rebels, including the pilot Kanan Jarrus, had learned of the plan, and, aboard the freighter Moonglow-72, began destroying the TIE fighters guarding the baradium haulers. The rebel group then initiated harassing fire on the haulers themselves, preventing the convoy from delivering their loads and scaring the pilots. Cauley tried to follow what the rogue freighter—dubbed Renegade One by Sloane—was doing but could not understand why it was was not destroying the freighters.[1]

Sloane, who had encountered Jarrus before, realized that he and the rebels were trying to scare off the other haulers, which Cauley confirmed, as any vessel that Moonglow-72 approached attempted to flee and turn off its ID transponder. The ensign then received word from one of the surviving TIE fighters that it was chasing a fleeing hauler that it had been escorting and needed instruction on what to do. Sloane began giving orders to run interference, but Cauley's communication was cut off with the fighter as it was destroyed by Renegade One. Infuriated, Sloane ordered a wing of fighters to destroy Jarrus and his freighter. However, they were unsuccessful, and the crew of the freighter ultimately prevented the destruction of Cynda. Vidian was exposed as having betrayed the Empire, as his scheme to destroy the planet would have ultimately resulted in a shortage of thorilide. The Gorse conflict was ended when the rebel Skelly detonated the baradium stored on Moonglow-72 while the freighter was docked aboard the Forager, destroying the larger vessel and killing the count.[1]

Personality and traitsEdit

"My lord?"
―Cauley is confused by Vidian's use of optical implants[src]

During the Gorse conflict, the human Cauley was young and fresh faced. Vidian's decision to feed the output from Cauley's data terminal into his optical implants caused the count to become stationary and stare into the distance, confusing Cauley and leading him to wonder what Vidian was doing. When Vidian gave permission for Cauley to return to his work, Captain Sloane imagined that he was relieved to not have the count looking over his shoulder.[1]

EquipmentEdit

While working at his terminal, Cauley wore a headset.[1]

Behind the scenesEdit

Cauley first appeared in the 2014 novel A New Dawn, written by John Jackson Miller. The novel was the first to be released in the Star Wars franchise's new canon.[3]

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 A New Dawn
  2. Star Wars Rebels: The Visual Guide states that Kanan Jarrus and Hera Syndulla met on Gorse, as depicted in the novel A New Dawn, six years prior to the events of Star Wars Rebels. Star Wars: Galactic Atlas states that Star Wars Rebels begins in the year 5 BBY, thereby dating the events of A New Dawn to 11 BBY.
  3. SWCustom-2011 Disney Publishing Worldwide and Random House Announce Relaunch of Star Wars Adult Fiction Line on StarWars.com (backup link)

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.