Fandom

Wookieepedia

Legacybattle1.jpg

135,459pages on
this wiki
Add New Page
Talk0
Full resolution (download)‎ (899 × 434 pixels, file size: 233 KB, MIME type: image/jpeg)
File:Legacybattle1.jpg
Information
Description

The Sith attack on Ossus

Source

Star Wars: Legacy 1

Licensing
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
of

  • Human/Legends

    Humans, taxonomically referred to as Homo sapiens, were the galaxy's most numerous and...

  • Kol Skywalker

    Kol Skywalker was a Jedi Master and head of the Jedi Council. Descended from the famous Luke...

  • Massacre at Ossus

    The Massacre at Ossus, equally the Massacre on Ossus, was a conflict that occurred in 130 ABY...

See full list >

File history

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

Date/TimeThumbnailDimensionsUserComment
current04:29, June 7, 2006Thumbnail for version as of 04:29, June 7, 2006899 × 434 (233 KB)Kuralyov (Talk | contribs)Opening attack on the Jedi Temple in the Sith Legacy War. From ''Star Wars Legacy 1''.

Metadata

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.