Warrior General Games

I know this game is private, but still have to post it as the play is definitely bugged. QB rolls out and waits (for a long time with a defender standing right in front of him waiting as well) until all the WRs have ran 80 yards down field, then he throws the ball 35 yards to a completely empty spot on the field.

http://glb2.warriorgeneral.com/game/replay/598/102526
http://glb2.warriorgeneral.com/game/replay/598/102563

If the game is private there's more than one bug...I can see the plays.

Originally posted by AirMcMVP
If the game is private there's more than one bug...I can see the plays.

I thought it was. Anyway, you agree that the plays probably aren't scripted right, on both sides of the ball.

Something definitely seems wonky.

Definately something wrong, why do I wanna say that LB is in QB Spy, so he's waiting for the QB to pass the line of scrimmage, but the waiting til the WR's are in the endzone and way out of range of any QB to throw to is quite hilarious

No one is open. It is a streaks play, so no one comes back.

Not a bug, we saw it a lot on the test server. If the spy wasn't there, you would have pulled that down and ran for 30 yards.

http://glb2.warriorgeneral.com/game/replay/504/84655

Just put your QB on scramble and your in business

Originally posted by Time Trial
No one is open. It is a streaks play, so no one comes back.

Not a bug, we saw it a lot on the test server. If the spy wasn't there, you would have pulled that down and ran for 30 yards.

The spy is definitely a bug. There is absolutely no way you can argue that he should stand around instead of sacking the QB

Originally posted by cavalier
The spy is definitely a bug. There is absolutely no way you can argue that he should stand around instead of sacking the QB

That's exactly what the spy does in this game. As long as the spy is there, the QB doesn't attempt to scramble. It is how it is coded.

Originally posted by Time Trial
That's exactly what the spy does in this game. As long as the spy is there, the QB doesn't attempt to scramble. It is how it is coded.

Yes, I understand how it is coded, that is pretty obvious from that replay. The issue is that it is simply stupid, or actually so far off reality that I would without doubt call it a bug.

Originally posted by cavalier
Yes, I understand how it is coded, that is pretty obvious from that replay. The issue is that it is simply stupid, or actually so far off reality that I would without doubt call it a bug.

There should be a setting to tell your spy to blitz after a certain amount of time or a certain distance from the pocket. As it is, you are lucky you had the spy. That play burns people with the RQB badly.

Originally posted by cavalier
Yes, I understand how it is coded, that is pretty obvious from that replay. The issue is that it is simply stupid, or actually so far off reality that I would without doubt call it a bug.

Yeah, I reckon I should update the spy to react kinda like the DE flats coverage - just rush the QB if he rolls out and gets close. Just standing there and staring him down from 3 feet away is kinda dumb lol.

Originally posted by Bort
Yeah, I reckon I should update the spy to react kinda like the DE flats coverage - just rush the QB if he rolls out and gets close. Just standing there and staring him down from 3 feet away is kinda dumb lol.

Sounds good. Thanks for the reply