Darth_Wredd_arrives_in_Carreras.jpg (download)‎ (612 × 480 pixels, file size: 65 KB, MIME type: image/jpeg)


File:Darth Wredd arrives in Carreras.jpg

Darth Wredd arrives at the Carreras G51 communications array.


Legacy 1: Prisoner of the Floating World, Part 1

Original designer / artist

Gabriel Hardman

Red copyrightThis image is an excerpt from the interior of a comic book and the copyright for it is most likely owned by either the publisher of the comic book or the writer(s) and/or artist(s) who produced the comic book in question. It is believed that the use of images of a panel or panels from the interior of a comic book to illustrate:
  • the scene or storyline depicted;
  • the copyrighted comic book character(s) or group(s) depicted on the excerpted panel(s) in question;
where no free alternative exists or can be created, on Wookieepedia, hosted on servers in the United States by Wikia, qualifies as fair use under United States copyright law. Any other uses of this image, on Wookieepedia or elsewhere, may be copyright infringement. See Copyrights for more information.

Appears on these pages

  • Ambush in the Surd Nebula

    This Ambush in the Surd Nebula was a short battle between the Galactic Federation Triumvirate...

  • Carreras Incident

    The Carreras Incident was a fleet action that took place in the Carreras system in the year 138...

File history

Click on a date/time to view the file as it appeared at that time.

current09:18, February 21, 2015Thumbnail for version as of 09:18, February 21, 2015612 × 480 (65 KB)Andykatib (Talk | contribs)==Summary== {{Information |attention= |description=Darth Wredd arrives at the Carreras G51 communications array |source=''Star Wars: Legacy 1: Prisoner of the Floating World, Part 1'' |artist=Gabriel Hardman |filespecs= |licensing={{Com...


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.