Does Tomb Raider's timed exclusivity make you want an Xbox One?
Maybe you would rather wait
Rise of the Tomb Raider launches next fall as a timed Xbox exclusive, and it will be fascinating to see how that affects Microsoft's fortunes.
There are millions of folks around the world keen on experiencing Lara Croft's next excursion. How badly and how soon they want to do that, though, remains to be seen.
Microsoft is making moves to ensure Xbox is a more attractive platform. It will have something that, at least for a moment in time, none of its competitors will be able to offer. Rise of the Tomb Raider will play a key role in the corporation's holiday push in 2015, influencing purchasing decisions at a time when that type of sway can be so incredibly valuable.
Of course, this particular exclusivity deal "has a duration." Unlike, first-party titles like Halo 5, there's a good chance Rise of the Tomb Raider will eventually wind up on other platforms. Consumers reticent to shell out for another console might just need to practice a little patience until Square Enix is allowed to cast a wider net.
The curious part about all this is that the game isn't just coming to Xbox One. It will be available for Xbox 360 as well. And a lot of folks already have one of those lying around. Rise of the Tomb Raider will sell better because of it, but people needn't necessarily run out and purchase Microsoft's new system. They might already own one that does the job.
Rise of the Tomb Raider then becomes another reason to get an Xbox One, rather than the reason. Keeping it off other platforms is a worthwhile business move for Microsoft. However, it doesn't seem like one likely to alter the landscape in dramatic fashion. It's a small victory, though. And those can add up over time.
What do you think? How will this week's big reveal affect you? Setup email comments
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.