It's commonly known that in 0.4.2, and every version previous, that DBs stop covering when a WR ends his route. The most common ways to see this are looking at routes like the 113 Post Flags or the 212 Quick Hits.
In the 113 Post Flags, the WR changes directions and heads up field as soon as he "touches" the sideline. When he makes this change of direction, the DB who has stopped covering has to identify the WR and try to get back into coverage. The same thing happens with the 212 Quick Hits except the WR touches the LOS and then runs a streak upfield. The DB usually stays at the LOS since the WR ends his route there and never gets back into coverage.
There are a number of exploit plays that do similar things. (And, why yes, I have built an entire game plan around them in the past although it's more effective to not do so since the QB logic gets effed by those plays.)
The stutter step logic is doing the same thing as Post Flags or Quick Hits. As soon as the WR stutters, the DB stops covering. He then has to identify a man he is supposed to cover and get back into coverage.
It's why low coverage LBs look so bad against TEs and RBs right now. They can't re-identify their man and end up on the other side of the field.
It's also why DBs are getting torched badly on long patterns.
Also, if 0.4.3 is released as is, I'm just going to build a long pass offense based around WRs and TEs that have 100 Route. I don't think SP even matters in this scenario except allowing the DB to catch up, and even then, it's iffy.
Last edited at 4/12/2018 9:46 am