Yavin 4

Outer Rim


Yavin system






Class breathable


Hot and sticky


Heavy enough

Primary terrain


Surface water

Shallow seas

Points of interest
  • Great Temple
  • Exar Kun's temple
  • Blueleaf temple
Native species
Official language

Galactic Basic Standard


Little to none

Major imports

Food, survival gear, etc.

Major exports

Jedi Knights

"This sure wasn't on the visitor's guide..."
―Luke Skywalker

Yavin 4 was the fourth moon of the gas giant planet Yavin Prime. Covered almost entirely with dense jungles and shallow, bountiful seas, it had a little bit of something for everybody. From as far back as 5,000 BBY, Yavin 4 would be among a select group of planets and moons that everybody in the galaxy and their brother would want to either visit, conquer, liberate, or obliterate. Eventually it was gotten rid of, but no one in this galaxy actually had the balls to do it.


"Kriff, kriff, kriff, kriff, kriff! Ship, get me the kriff outta here!"
―Naga Sadow, running away to Yavin

Yavin 4 was first colonized by the ancient Sith Lord Naga Sadow, when he fled the ass-kicking that the Sith received at the hands of the Galactic Republic and Jedi Order. A thousand years later, the surface would be dotted with many ancient temples, built by native Massassi who labored as slaves for Dark Lord of the Sith Exar Kun. After the moon was practically leveled by the Jedi and Republic at the end of the Great Sith War, not much happened there for the next four millennia, unless you count the interminable screaming from Kun's disembodied spirit.

Rebels and rodentsEdit

"It is green."
C-3PO, upon arrival at Yavin

Another temple, after the Sith magic wore off.

Over time, Yavin's jungle fever returned, and it was once again lush with life, most of it eager to either annoy the piss out of or eat travelers and explorers. The temples, cursed "blessed" with Sith magic, remained as intact and complete as they were when the Massassi finished building them. The moon's features made it seem like a great place to plant a secret base when the Rebel Alliance arrived there in 0 BBY. Of course, someone had to go and ruin the fun by letting the Galactic Empire find the place through a tracking device mounted on the Millennium Falcon. Next thing you know, this huge Big Ball Planet Destroying Thing shows up packing a superlaser, and the Rebels have to go and beat them off. Luke Skywalker, naturally, lands the lucky shot, the day is saved, but now the Rebels have to get the kriff out of there.

Blissfully unaware that the Dark Side of the Force infested the place like an oily stain, Luke went back to Yavin ten years later to set up his Jedi Academy. Ipso facto, ergo, et. al., the whole place went to hell in a handcart when first Gantoris died in a Force fire, then Kyp Durron got all angry and blew up some suns, after first knocking Luke out of his own body. Corran Horn ended up having to save the day (and getting none of the credit, the bastards), and all seemingly returned to normal after Exar Kun's aforementioned spirit was liquidated.

Thus spoketh the VongEdit

And so, after twenty years of pumping out more Jedi punks, the moon met its final end when the Yuuzhan Vong invaded the galaxy and took the place over. More angsty teenagers did battle alongside muscle-bound and brainless warriors, more blood got spilled, and the entire moon was basically turned into a snack for biots and bloated beasts. Needless to say, no one was going back there any time soon.

This article is called Yavin 4. Yavin 4 has been written from a simple, Ric Olié point of view. A non-simple version of Yavin 4 can be read on Darthipedia. Darthipedia is the Star Wars Humor Wiki.
Born without a sense of humor? We are inspired by your courageous struggle. …Just kidding. Get the hell out of here and go read Wookiepedia's "real" article on Yavin 4.



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.