Tuesday, 23 September 2014

Star Wars: Commander


I started playing this the day it came out. I think it was last week. I love a bit of button pushing to keep me occupied on my phone or tablet. I've got a few games I regularly check every day and I'm constantly on the look out for new ones. I generally go with big franchises when it comes to Android games because, let's face it, the games themselves really aren't that good. It's just the familiarity that keeps me coming back for more. As a big fan of everything Star Wars, it was a no-brainer to try Star Wars: Commander out to see if it would make my small stable of regular, quick-check games. 

It calls itself a RTS, but there is very little strategy to it. When you attack, you simply plonk all your men down and watch them blow everything up, gaining you three stars every time. When you defend you just watch your turrets take care on the attackers and gain three stars every time. This is not very rewarding at all. There are also major film characters available to use right from the start of the game but cannot be used to attack with.

Epic battles... Really?!


This game is much more of a City Builder than a RTS and when it comes to City Builders, there's a lot better on offer such as The Simpsons: Tapped Out, Family Guy: The Quest For Stuff or Dragons: Rise of Berk. All of which are very simple but ultimately satisfying as you care about the characters you're playing with. You'd think this would be the same for a Star Wars game. I really don't know how they've got it so wrong. Well Darth Vader's voice is pretty terrible actually. That's one thing. But I simply do not care about anything that happens in the game. Saying that, if this wasn't a Star Wars game, it would have lasted less than a day with me. As it is, I've been tapping away now for a few days. I think I'm hoping, desperately hoping, that this isn't yet another rubbish Star Wars game. 

What have been your biggest franchise disappointments?

No comments:

Post a Comment