Originally posted by tautology
The "and goal" bug is ubiquitous, as SteelersInsider has said. If you have situational calls based on down and distance near the goal line, you encounter this problem eventually.
The problem was that "4th & G" was treated as "4th & 0" once in a while, however, it is not always being treated as 4th & 0. This is why Bort had hard time reproducing the bug since it doesn't always fail. Maybe Bort has already fixed the bug and that's no one talking about it now. But I remember when it first happened, there were about 4 or 5 posts about it. It's not a "every team sees it" bug since it requires certain setting in AI and it doesn't always happen.
Think about it, both problems are pretty similar that it doesn't always fail under same condition. The main difference is that the "and goal' bug is easier to notice while the current issue is harder.
The "and goal" bug is ubiquitous, as SteelersInsider has said. If you have situational calls based on down and distance near the goal line, you encounter this problem eventually.
The problem was that "4th & G" was treated as "4th & 0" once in a while, however, it is not always being treated as 4th & 0. This is why Bort had hard time reproducing the bug since it doesn't always fail. Maybe Bort has already fixed the bug and that's no one talking about it now. But I remember when it first happened, there were about 4 or 5 posts about it. It's not a "every team sees it" bug since it requires certain setting in AI and it doesn't always happen.
Think about it, both problems are pretty similar that it doesn't always fail under same condition. The main difference is that the "and goal' bug is easier to notice while the current issue is harder.






























