Conference on Kashyyyk

135,506pages on
this wiki
Add New Page
Talk0 Share

The title of this article is conjectural.

Although this article is based on official information from the Star Wars Legends continuity, the actual name of this subject is pure conjecture.

"Too important this conference is to allow it to be disrupted by the Separatists."
Yoda discussing the conference with Obi-Wan Kenobi[src]

A conference was held by the native Wookiees of the planet Kashyyyk during the Clone Wars.

The conferenceEdit

The security for the conference was over seen by Jedi Master Obi-Wan Kenobi and Jedi Grand Master Yoda was also in attendance sent by the Wookiees allies the Galactic Republic and the Jedi Order. The Jedi were aware that some Wookiees were becoming unhappy with the Republic alliance, but the conference was considered to important to be delayed.

All attendees of the conference, including the Wookiee Chewbacca, had to pass through a holoscanner to enter the building in which the event was held to check for weapons. A ray shield also protected the speakers against blaster fire from the audience. One Wookiee, the decorated war hero general Attimun, managed to sneak a dismantled explosive charge launcher through the scanner and used the weapon to attack the speakers from the tree tops during the conference. Kenobi successfully attacked and subdued the Wookiee before he could deal to much damage who was then immediately arrested. Attimun was revealed to have become enraged with the Republic after the death of his wife and two children during the Clone Wars.[1]

Behind the scenesEdit

The conference on Kashyyyk first appeared in the comic Incident on Kashyyyk written by Mike W. Barr and illustrated by Tanya Roberts. It was published in Star Wars: The Clone Wars Comic UK 6.37 in 2012.


Notes and referencesEdit

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.