PAX: Sanctum 2 upgrades the original in every way
No Mac version planned
When the original Sanctum came out, it took the indie world by storm. As a first person tower defense game in 2011 (that kicked ass by the way), it was pretty unique. Coffee Stain Studios looks to repeat that success with a fully featured sequel, and if the playable build I sat down with at PAX East is anything to go by, they're going to surpass their prior efforts.
No joke, everything is better in Sanctum 2. There's more playable characters, more options for character development, more robust levels (and more of them), and a much better tutorial system. In the first game, I noticed that quite a few people had trouble acclimating themselves to the way the game worked -- after all, an FPS TD hybrid isn't the easiest thing to pick up and play.
But through a pretty simplistic FPS style action tutorial, it's really easy to get up and go with Sanctum 2. I checked out out the all new campaign, complete with actual story this time around, and a bit of gameplay with the new characters, which all feel pretty different. It feels like a more...complete game this time around, and not just a niche experience like the vibe the original gave off at times.
I had a chance to speak to developer Oscar Jilsen, who said that this tutorial would naturally help players on consoles who aren't used to the genre. Also, since the original Sanctum took quite a while to port to Mac, I wanted to check on the status of a Mac version of Sanctum 2.
Jilsen immediately put this idea to rest though, stating that it was "a great deal of effort to work with Macs on such a small team," and that Sanctum 2 was not in the cards on the Mac platform. It will however, be available on PC, XBLA, and PSN.
Photo Gallery: (7 images) Setup email comments
Click to zoom - browse by swipe, or use arrow keys
Please report harassment, spam, and hate speech to our community fisters
, 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.