In fact, when I look at the games I love the most, a good number of them tend to fall on the punishing side.
To be sure, it’s not that I don’t like a challenge. The problem is that it perhaps expects you to think too far outside the box at times. It’s a brutal, uncompromising experience that frequently forces you to think outside the box to win. In fact, in the strictest terms, Nexus is exactly what I hoped it would be. You’re given a mission and a set fleet of ships to complete it. Nonetheless, going into Nexus: The Jupiter Incident, I was excited in no small part because what I’d heard about the game pointed to it pretty much being exactly that. Suffice it to say that this is a challenge I don’t usually win at.
I have what I have and when my forces dwindle down to nothing that’s it. I’ll build a carrier, a handful of frigates, and a few squadrons of fighters and bombers and then that’s all I’ll allow myself.
One of my favorite games is Homeworld and one of my favorite things to do in it is to load up a multiplayer match against a couple of AI commanders and then try to take them down with limited resources. Originally released in 2004, Nexus: The Jupiter Incident drops players into the commander’s chair and tasks them with guiding their fleets to victory in an interstellar conflict involving alien races, sentient machines and, of course, big, flashy explosions.
