Tap Strafe
What is current state of Tap Strafe? Developers wrote that they plan to remove it, but it wasn't done. Is it because many pro players was against it? or developers forgot how to program? or they hav...
Forum Discussion
@SlivPTS When they tested its removal, in private servers, it messed up the whole movement aspect of the engine/game. And you can add the massive backlash to Respawn too. Maybe @pandareno1999 can explain it better than me on the exact reason why they tried removing it. LOL.
Short History of Tap strafing
It feels “hackish” because it’s a movement bug that was not intentionally added by the developers. Tap strafing is/was a thing with other FPS games using the source engine (Apex/TF engine). It was then re-discovered in Titanfall 2. Only at around the start of season 6 where it was re-re-discovered but this time in apex. Mokeysniper, a well known apex movement technique player/content creator who actively looks for other movement techniques in apex, made a video investigating it’s potential in the game. This video was seen by a lot of pros/streamers and started to do it too. Then it spread like wildfire and it’s now popular as you know it.
Sidenote: This was the same thing I was pointing at when talking about the Taxi using the speed glitch issue. People will copy popular streamers. The difference is that tap strafing isn’t as OP as that insane speed glitch.
- @Cheese9Man "it messed up the whole movement aspect of the engine/game."
why not simply disallow bind forward move on scroll wheel? It will not break anything.- @SlivPTS I added 2 paragraphs to my original post. Lol.
“Why not simplay disallow bind forward move on scroll wheel?”
Now this is where my “expertise” end. As far as I know, it is steam (not Apex) that allows you to bind different types of keys. Some controller players can even tap strafe where they use R3 for that button. It’s called “Flick Strafe”.https://medium.com/@swaysd0/lurch-and-tap-strafing-4b17ff63621e
From the last word we got the other week from Jay Biebs, it sounds like the removal of tap strafing is still in the works, just proving tricky to execute. The solution by removing ability to bid scroll wheel? On the face of it, it seems a simple solution. I suspect that, were it that simple, it'd obviously already have been done and we wouldn't still be talking about it. I have forgotten what the argument was against disallowing scroll wheel bindings, but I remember it being convincing enough. I'll leave that bit to your own google searching. Cheers!
@SlivPTS wrote:
@Cheese9Man"it messed up the whole movement aspect of the engine/game."
why not simply disallow bind forward move on scroll wheel? It will not break anything.Then you merge from origin to steam and rebind it there.... or rebind your mousewheel in windows and go from there.
If you are to remove tap strafe you need to remove the move not the bind, but to remove the move that messed up the entire movement code of the apex engine so they decided not to touch it as cheese here says.
@ZkepzThey can fix problem in many ways. Not always hardest way is best way.
I hope they understand that longer it will take to remove tap-strafe = more negative backlash will be. To me it's weird that it takes so long.
Also they can check for scroll wheel input when strafing and ignore strafe when scroll wheel input is detected.It can be as simple as:
void AirMovement()
if(scrollWheelInput != 0) return;
//streafe movement code here
