Kinect Star Wars priced and dated, adds space battles



3:00 PM on 02.07.2012

Just in time to make people reconsider watching Jar Jar in horrifying 3D, Kinect Star Wars has finally been given an April 3, 2012 release date and a $49.99 price tag. The delicious limited edition console bundle will go on sale for $449.99 on the same date.

Some of the new additions to the game include space battles, speeder bikes and landspeeders, and a Galactic Dance Off mode that will hopefully throw the loser into a Rancor pit for failing to appease the slaver overlords. If you buy the limited edition bundle, they'll throw an exclusive C-3PO unlockable for the Galactic Dance Off mode in the mix.

In case you've forgotten, this brings Kinect Star Wars to five modes. Jedi Destiny: Dark Side Rising appears to be the main campaign mode they've shown off before, now with speeder bikes and space battles. Podracing is, well, podracing. Rancor Rampage lets you stomp around Naboo and Tatooine from the looks of the screenshots. Duels of Fate lets you fight against Seperatist and Sith scum, such as Count Dooku and Darth Vader, in lightsaber duels.

Finally, the Galactic Dance Off mode is "loaded with Star Wars-themed pop tunes where those still honing their Jedi skills can take a break to battle Darth Vader on the dance floor or bust a move 'Solo style.'" Oh dear. Being slowly digested over a thousand years is not enough for whoever came up with that pun.

It looks like Kinect Star Wars has some more meat to it after the delays, and some of these new modes will probably make better use of the advances in the platform technology than shouting "Lightsaber on!" If there ends up being a Kaadu-riding minigame, though, count me out for this one.

Check out some of the screenshots below.



Come for the news, stay for the people:

Get comment replies by email.     settings



Unsavory comments? Please report harassment, spam, and hate speech to our comment moderators

Can't see comments? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*].disqus.com   to your security software's whitelist.