In the same game, I also had a weird challenge situation. My opponent had a 4th and 1 in my territory and went for it. I stopped the runner around the 1st down marker. The game gave him the first down, but I thought I stopped him short, so I challenged the spot of the ball. The announcers said they thought I was going to win the challenge, and I did, but my opponent kept possession of the ball. I don't know if this is excellent programming (putting in a challenge scenario where one can win the challenge but still lose the war because even the correct spot would be a first down) or a bug. I give the benefit of the doubt, though, and assume it's the former.
One definite bug, one interesting observation
Collapse
Recommended Videos
Collapse
X
-
One definite bug, one interesting observation
I was playing the Skins against the Cowboys online (Xbox Live) yesterday evening, and I encountered a penalty bug. I was on D, and my opponent (line of scrimmage @ about the Dal 30) threw an interception. Before the interception, I hit his QB late, drawing a flag. Matt Bowen picked off the pass and landed at the WAS 48, where he was touched down. Here are the options the penalty screen gave my opponent: Accept, DAL ball on the WAS 33. Decline, WAS ball on the WAS 48. Obviously, the game failed to account for the change of possession, giving my opponent a 22 yard bonus (the penalty should have given him the ball at the DAL 45).
In the same game, I also had a weird challenge situation. My opponent had a 4th and 1 in my territory and went for it. I stopped the runner around the 1st down marker. The game gave him the first down, but I thought I stopped him short, so I challenged the spot of the ball. The announcers said they thought I was going to win the challenge, and I did, but my opponent kept possession of the ball. I don't know if this is excellent programming (putting in a challenge scenario where one can win the challenge but still lose the war because even the correct spot would be a first down) or a bug. I give the benefit of the doubt, though, and assume it's the former.Tags: None -
Re: One definite bug, one interesting observation
Your second scenerio basically happened to me last night. I went for it on 4th and 1 late in the game and I was stopped short of a first down. I thought I made it, so I challenged the call. The call on the field was overturned, yet it was still the other teams ball 1st and 10 afterwards! Oh well... at least I didn't lose a timeout.LET'S GO FLYERS, YANKEES, DOLPHINS!!! -
Re: One definite bug, one interesting observation
Your second scenerio basically happened to me last night. I went for it on 4th and 1 late in the game and I was stopped short of a first down. I thought I made it, so I challenged the call. The call on the field was overturned, yet it was still the other teams ball 1st and 10 afterwards! Oh well... at least I didn't lose a timeout.LET'S GO FLYERS, YANKEES, DOLPHINS!!!Comment
-
Re: One definite bug, one interesting observation
Your second scenerio basically happened to me last night. I went for it on 4th and 1 late in the game and I was stopped short of a first down. I thought I made it, so I challenged the call. The call on the field was overturned, yet it was still the other teams ball 1st and 10 afterwards! Oh well... at least I didn't lose a timeout.LET'S GO FLYERS, YANKEES, DOLPHINS!!!Comment
-
Re: One definite bug, one interesting observation
</font><blockquote><font class="small">Quote:</font><hr />
Chrono said:
Your second scenerio basically happened to me last night. I went for it on 4th and 1 late in the game and I was stopped short of a first down. I thought I made it, so I challenged the call. The call on the field was overturned, yet it was still the other teams ball 1st and 10 afterwards! Oh well... at least I didn't lose a timeout.
<hr /></blockquote><font class="post">
I saw that exact same call while watching a cpu vs cpu game. Thought it was odd and it should have been a first down but oh well, it's not a game killer.Comment
-
Re: One definite bug, one interesting observation
</font><blockquote><font class="small">Quote:</font><hr />
Chrono said:
Your second scenerio basically happened to me last night. I went for it on 4th and 1 late in the game and I was stopped short of a first down. I thought I made it, so I challenged the call. The call on the field was overturned, yet it was still the other teams ball 1st and 10 afterwards! Oh well... at least I didn't lose a timeout.
<hr /></blockquote><font class="post">
I saw that exact same call while watching a cpu vs cpu game. Thought it was odd and it should have been a first down but oh well, it's not a game killer.Comment
-
Re: One definite bug, one interesting observation
</font><blockquote><font class="small">Quote:</font><hr />
Chrono said:
Your second scenerio basically happened to me last night. I went for it on 4th and 1 late in the game and I was stopped short of a first down. I thought I made it, so I challenged the call. The call on the field was overturned, yet it was still the other teams ball 1st and 10 afterwards! Oh well... at least I didn't lose a timeout.
<hr /></blockquote><font class="post">
I saw that exact same call while watching a cpu vs cpu game. Thought it was odd and it should have been a first down but oh well, it's not a game killer.Comment
-
Re: One definite bug, one interesting observation
When they showed the replay I could see my running back's knee hit the ground earlier then I thought, and I expected the call to stand. I was actually surprised when they said it was overturned, so who knows... they may have actually moved the ball back a few inches!LET'S GO FLYERS, YANKEES, DOLPHINS!!!Comment
-
Re: One definite bug, one interesting observation
When they showed the replay I could see my running back's knee hit the ground earlier then I thought, and I expected the call to stand. I was actually surprised when they said it was overturned, so who knows... they may have actually moved the ball back a few inches!LET'S GO FLYERS, YANKEES, DOLPHINS!!!Comment
-
Re: One definite bug, one interesting observation
When they showed the replay I could see my running back's knee hit the ground earlier then I thought, and I expected the call to stand. I was actually surprised when they said it was overturned, so who knows... they may have actually moved the ball back a few inches!LET'S GO FLYERS, YANKEES, DOLPHINS!!!Comment
Comment