*Sigh* It's happening. · 12:59pm Jun 10th, 2015
I was afraid of this. I thought it would take several weeks, but it's only taken two.
Because of that sweet image of Buck in Halo 5 that debuted yesterday, I turned on my Xbox One for the first time in 14 days, and downloaded ODST for the Master Chief Collection. Looked pretty enough, and I stared at my screen like a man and started the campaign on Heroic.
Took me 20 minutes to remember where to go (sue me, it's been five years) as the Rookie, and it finally dawned on me in the first encounter of Buck's mission:
I can't fucking aim with a controller anymore.
Okay, I can, but it's so damned clunky. Fourteen days on Skyrim and Titanfall with a mouse and keyboard have hindered my thumbstick skills considerably. I've always told myself that K/D is something only tryhards and CoD kiddies keep track of. I think that was partly my blatantly average FPS skills talking. Throughout Halo, CoD, Battlefield, and Titanfall, my overall K/D has been in the 0.8-1.2 range. Not noteworthy at all.
But a week with Titanfall PC has made me amazed at my own performance. The first 20 games, I skyrocketed to a 2.5 K/D versus other players (vs grunts is 10.2, not sure why that's even tracked). That's since fallen to a 2.1, but still, it's a number I never came close to on consoles.
Just wondering what this is going to mean when Halo 5 comes out in October, where I'll probably be worse than ever, unless I buy one of those keyboard-and-mouse adapters, which I hear aren't perfect.
Is that a thing? I mean, well, if that actually worked properly, wouldn't that be massively unfair to everyone that uses a controller? There's a reason we don't even entertain the idea of using the same servers for consoles and pc's.
Seriously though, this is all very familiar to me.
3136700 Microsoft has stated that it's not against the Terms of Service.
When it comes to individual titles, however, developers can ban you from multiplayer modes if detected.
3136727
Sounds like a surprisingly good policy.