Oh... At 16:52, 17:19 and 17:48 in the video, I didn't fully understand what was going on. Some guy on Gamespot tried to tell me two months ago that Steam users have complained about the mouse and keyboard causing unintended actions. I pressed him on it, but he didn't explain, because he's a 100 percent controller user probably. Anyway, console players too have to deal with the run button controlling access to floor grills, cover, railings and such. But only the weirdos like me who play with a M/KB have to deal with the single smoke pellet overriding the aiming of all gadgets when discovered and occasional unintended aiming (which I guess then becomes counter when attempted again) when trying to perform silent takedowns.
Xbox controller: Y = silent takedown, counter
Right mouse button = silent takedown, counter AND gadgets
My video lies that both M/KB and controller users suffer the same shared buttons.
Old:
The predator maps are highly context-sensitive, with playground floor grills, catwalks, gargoyles and other designated spots [1] favored over natural movement, so densely packed together that the player inevitably performs the wrong actions or struggles to prompt the desired one. They crouch by a railing in order to hang, but the game keeps offering corner cover [2]. They try to go under a grate, but the game pulls them towards another waist-high object [3]. You try to do a silent takedown, but Batman takes out his last used item and then raises his fists. The run button also being the interact button while crouched means that Batman will attach to these waist-high objects as you switch back and forth between the crouch and upright movement [4]. Be careful that you don't drop Batman's only smoke grenade as you try to escape, since it supplants all of his other tools when he is discovered, while the prompt calls attention to itself in the top-middle of the screen. You can't even separate from certain walls without giving away your position [5]. The context-sensitive controls can also make taking down enemies quite finicky, depending on what they are doing. [6] Here the available action changes from Silent Takedown to Corner Cover and Batman stands up and raises his fists. The functions that the buttons share are the same whether you use a controller or a mouse and keyboard [7]. They cannot be separated.
New:
The predator maps are highly context-sensitive, with playground floor grills, catwalks, gargoyles and other designated spots favored over natural movement, so densely packed together that the player inevitably performs the wrong actions or struggles to prompt the desired one. They crouch by a railing in order to hang, but the game keeps offering corner cover. They try to go under a grate, but the game pulls them towards another waist-high object. The run button also being the interact button while crouched means that Batman will attach to these waist-high objects as you switch back and forth between the crouch and upright movement. Mouse and keyboard users have all these functions assigned the Spacebar and controller users to the bottom face button. Everyone is affected. But at least for controller users the smoke pellet only takes over the counter and stealth takedowns when they are discovered. For those of us who use a mouse and keyboard, the single smoke pellet that Batman carries also supplants the aiming of all other gadgets, making it even easier to deploy it by accident. Controller users also don't aim gadgets when they mean to perform stealth takedowns. Both are handled with the right mouse button, unfortunately. You can't even separate from certain walls without giving away your position.
Now that I understand, I moved the scene at 17:48 to the part where I say, "In fact, I would let the player take [grab] enemies in combat as well, if they can get behind or beside them. No reason for the mechanics to change just because Batman has been discovered." Since it's still twitchy context-sensitive BS, context being mechanical transitions from action to stealth.
I hoped that my computer finished encoding the corrected version when I got home today, but it went to sleep again, causing Shotcut to fail again. I even put the power settings on "high performance." It shouldn't be the "Turn off disc after" setting, since it encoded several hours before going to sleep and failing. Whatever, will just encode while I'm home and awake. Not even embarrassed about uploading the video again, since I've only posted it here and it got almost no traffic compared to the skill videos with basically shitpost titles. But I don't care. Will keep it as the main video (corrected one, I mean, after it's uploaded).
