Warrior General Games

Ben Franklin (specifically IN4) is apparently just too fast. Notice he freezes and then once the catch is made he resumes movement.

Dot is 138.72 speed, 85.49 agility w/o Special Teamer, Streaky, and Track Star factored in.

http://goallineblitz.com/game/replay.pl?game_id=1448517&pbp_id=4362923
http://goallineblitz.com/game/replay.pl?game_id=1448517&pbp_id=4363606
http://goallineblitz.com/game/replay.pl?game_id=1448517&pbp_id=4366471
http://goallineblitz.com/game/replay.pl?game_id=1448517&pbp_id=4366919

Does not happen all the time (same game):
http://goallineblitz.com/game/replay.pl?game_id=1448517&pbp_id=4364577

Haven't done enough examination to determine if this is unique to IN4, but my gut tells me it's across all the ST positions. I remember it coming up before on some other issue. Could have been reported into Bugzilla in the past, I don't remember.

I think this is part of the code that stops all the coverage players at that point until the ball is fielded.

We've obviously seen this numerous times with muffed catches by the returner and everyone stops until the ball is picked up, but I didn't realize it happened on regular returns where the ball just hasn't been caught yet.

We'll need replays from other teams for a decent sample size, but I'm willing to send this up to double check it.

Needs more info for replays

Getting additional replays would be much easier with the use of the test server. Locating ST'ers with the player in the above replay's speed/agility is pretty damn difficult.

Just about every LB'er with his speed is used as a blitzer and doesn't have Special Teamer.

I'll poke around, I guess. Just seems a bit superfluous. It's a recognized bug and I've given enough information to easily replicate it should Bort need to.

http://goallineblitz.com/game/replay.pl?game_id=1448506&pbp_id=4355771

Happens to the dot named 'KR and PR' here.

http://goallineblitz.com/game/replay.pl?game_id=1491907&pbp_id=4030182

Happens to both (HULK) (BIGHANDS) and Nate "NateRob" Robinson.

Originally posted by VolBrian
I think this is part of the code that stops all the coverage players at that point until the ball is fielded.



I don't think this has to do with that change.. If that were the case in all the replays he submitted the player in question would stop at "the wall" at the same time and distance as any other player.. When in fact in every replay there the player in question gets stopped a good 2 to 3 yards behind where the furthest dot makes it to... therefore suggesting that theres a glitch and the player gets stuck.. however it would be hard to figure out why this is indeed happening since it doesnt seem to be the same position each time.. and in the replays submitted the ball does not always travel in the same direction and it doesnt seem to be happening at the same distance away from the returner.. This could very well be a bug but would be difficult to figure out exactly what is happening.

Good enough for me I suppose with the other teams being included in examples.

Likely a bug

Originally posted by _Mentalist_
Originally posted by VolBrian

I think this is part of the code that stops all the coverage players at that point until the ball is fielded.



I don't think this has to do with that change.. If that were the case in all the replays he submitted the player in question would stop at "the wall" at the same time and distance as any other player.. When in fact in every replay there the player in question gets stopped a good 2 to 3 yards behind where the furthest dot makes it to... therefore suggesting that theres a glitch and the player gets stuck.. however it would be hard to figure out why this is indeed happening since it doesnt seem to be the same position each time.. and in the replays submitted the ball does not always travel in the same direction and it doesnt seem to be happening at the same distance away from the returner.. This could very well be a bug but would be difficult to figure out exactly what is happening.


It can always be duplicated on the test server for Bort to pull the trace data.

Another one to get looked at. Sending up.

doobas™

Still not filed?

I wonder if this has anything to do with this one:

http://goallineblitz.com/game/forum_thread.pl?thread_id=4419341

Not sure if this is a bug, but there might definitely be some inconsistency in which the Kickoff coverage is coded.

99.999999999% sure this is working as intended (as i remember that bort coded dots to stop if they reached a certain point downfield to prevent weird situations of recovering the football- more for lower levels) any other QA mods remember this?

As for why it's inconsistent my best guess would be shoddy collision detection (dot probably passed right through the "stop point" the times he didn't stop, w/o ever actually visit the point where bort codes them to stop)

locking this up and referencing to a duplicate thread in the QA forum

locked