Fandom

Wookieepedia

The Force Awakens, Part IV

133,942pages on
this wiki
Add New Page
Talk0 Share

The Force Awakens, Part IV is the fourth issue of the six-part Marvel comic book miniseries Star Wars: The Force Awakens, an adaptation of the film of the same name. The issue, released on September 14, 2016, was written by Chuck Wendig, with art by Luke Ross.[1]

Publisher's summaryEdit

Plot summaryEdit

Episode VII, Part IV
THE FORCE AWAKENS
Luke Skywalker has vanished. In his absence, the
sinister First Order has risen from the ashes of
the Empire and will not rest until the last Jedi has
been destroyed. The First Order and the Resistance
are in desperate search for a map leading directly to
Skywalker that is hidden inside the Resistance droid
BB-8.

After Finn, a former stormtrooper, escapes the First
Order, he crash-lands on Jakku where Rey, a young
scavenger, has found BB-8. Rey, Finn, and BB-8
become allies and hijack the Millennium Falcon to
evade their would-be captors, but are caught by
smugglers Han Solo and Chewbacca. Han informs the
group that the map to Skywalker is not complete, and
they set off to find the rest.

Once they arrive on the planet Takodana, the crew
meets Maz Kanata. Maz offers Finn a choice to
disappear to the Outer Rim, and he takes it–leaving
Rey, who hears a calling in the distance. Following
the sound, she discovers a mysterious weapon....

AppearancesEdit

By type 
Characters Creatures Droid models Events Locations
Organizations and titles Sentient species Vehicles and vessels Weapons and technology Miscellanea

Characters

Droid models

Events

Locations

Organizations and titles

Sentient species

Vehicles and vessels

Weapons and technology

Miscellanea


Cover galleryEdit

BibliographyEdit

Notes and referencesEdit

External linksEdit

In other languages

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.