Jade from Beyond Good & Evil skin unlocked by completing Prince of Persia
2:40 PM on 12.01.2008 // Nick Chester
Last week, we ran a silly little article called "Top 5 Ubisoft character skins we'd like to see in Prince of Persia." In it, I joked that one of them I'd like to see is Jade from Ubisoft's "cult hit" Beyond Good & Evil. Well, someone must have been listening (or I'm psychically linked to the Prince of Persia team), because imagine my surprise when I found that completing the game unlocked just that -- a Jade skin for the Prince's magical sidekick, Elika.
Selectable from the game's "Skin Manager" in the "Extras" menu, the skin simply changes her outfit to the tiny white top and green number made famous by Jade. There's even a bow staff on her back and a pouch that hangs by her side, but neither perform any in-game function; magical Elika has no need for such things, anyhow.
The Jade skin joins the free skin of Assassin's Creed's Altair for the Prince, which is available simply by signing up for a Ubisoft.com account and linking it to your game. (Doing it on the PlayStation 3 was a snap; the game brought up the web browser to initiate sign-up and everything.) Also available with selected limited edition copies of the game are two additional skins -- the Prince of The Sands of Time trilogy, as well as a Farrah skin for Elika.
This means there's two more skin slots for both Elika and the Prince open. I wonder if either of them will be the "dog whisperer," Cesar Millan. One can only dream ...
Prince of Persia is being delivered to stores by storks right now, and our full review will go live tomorrow at 10 A.M. PST.
[Note: All images were taken with a digital camera directly off of a television, hence the questionable quality.]
Photo Gallery: (4 images) Setup email comments
Click to zoom - browse by swipe, or use arrow keys
Please report harassment, spam, and hate speech to our moderators
, and flag the user (we will ban users dishing bad karma
). Can't see comments?
Apps like Avast
or browser extensions
can cause it. You can fix it by adding *.disqus.com to your whitelists.