Originally posted by rjssob
No offense, but that explanation is from you or from Bort? What defines the end of their route? A crossing route and you are going to say that the WR will just stop like he ran into a brick wall while the QB does not know this and attempts to the lead the WR? This has not happened in the past that I have seen and is almost certainly a bug or at the very least poor code. I could see that explanation somewhat on a Curl or Hook route, but that is just crazy...Here is a sample:
http://goallineblitz.com/game/replay.pl?game_id=1309299&pbp_id=7313591
WR1 has the CB beat but decides to stop, while WR3 running the exact route keeps going? Nobody outside the targeted receiver breaks his route here...I just explain from experience and I do know that,
as currently coded, receivers will stop once they have reached the end of the route as the play is coded. That route may end exactly where the diagram shows it to, or it may extend a bit farther, but if your QB holds the ball long enough without being sacked or throwing it, you'll see them stop.
In the play you posted, everyone reaches a route end and stops with the exception of WR1 who the ball is passed to. The HB stops at the sideline, WR2 at the end of the hook route, the TE at the end of the fly route on the backline, and WR3 at the end of the deep slant.
I'm not of the mindset that this is how it
should be, just that it is how it is currently set up and not a bug.