User Pass
Home Sign Up Contact Log In
Forum > Goal Line Blitz > WTF Is This? (Return Man Stops Running Multiple Times)
Page:
 
Mightyhalo
offline
Link
 
It's his piss poor agility. He knows the defenders are going to catch him so he tries to make a cut, but his weak agility slows him down too much.

He is level 2, he has a long way to go.
 
Hagalaz
offline
Link
 
Originally posted by Mightyhalo
It's his piss poor agility. He knows the defenders are going to catch him so he tries to make a cut, but his weak agility slows him down too much.

He is level 2, he has a long way to go.


50 agility should be enough at that level to run in balanced.

This is a bug, plain and simple. Or better yet, a crappy implementation of the pathing code. There is no reason EVER why a HB with open road should stop. NEVER.
 
Mightyhalo
offline
Link
 
Originally posted by Hagalaz
50 agility should be enough at that level to run in balanced.

This is a bug, plain and simple. Or better yet, a crappy implementation of the pathing code. There is no reason EVER why a HB with open road should stop. NEVER.


It's always been this way especially for a level 2 dot. Heck I've seen loss of speed from lv 70's making cuts. Cuts cause a loss in speed for the offensive player but not as much for the defender even though they said they tweaked that this season.
Edited by Mightyhalo on Apr 11, 2010 07:24:33
 
Hagalaz
offline
Link
 
Originally posted by Mightyhalo
It's always been this way especially for a level 2 dot. Heck I've seen loss of speed from lv 70's making cuts. Cuts cause a loss in speed for the offensive player but not as much for the defender even though they said they tweaked that this season.


You don't get it. Why would you cut if your road to the end zone was clear? Just run full speed ahead!
 
SmoothCaramel
offline
Link
 
Originally posted by Hagalaz
Originally posted by Mightyhalo

It's always been this way especially for a level 2 dot. Heck I've seen loss of speed from lv 70's making cuts. Cuts cause a loss in speed for the offensive player but not as much for the defender even though they said they tweaked that this season.


You don't get it. Why would you cut if your road to the end zone was clear? Just run full speed ahead!


I understand what you're saying, but I think that it's a new change to the slider for this season. If you want him to run straight then set it to -100 to -70. Especially at low levels, err on the Power side. I think that what others have said about Vision, Stamina and Confidence being involved has something to do with it too.
 
Hagalaz
offline
Link
 
Originally posted by SmoothCaramel
I understand what you're saying, but I think that it's a new change to the slider for this season. If you want him to run straight then set it to -100 to -70. Especially at low levels, err on the Power side. I think that what others have said about Vision, Stamina and Confidence being involved has something to do with it too.


I don't mean go straight ahead all the time, I mean _ONLY_ when the road is clear. If there's no one ahead and the only threats come from behind, the best course if action is to run for it, not try to shake them as if they were in front of you.

It's either a bug or crappy coding. Neither of which good for the game.
 
uoY_redruM
offline
Link
 
Originally posted by Hagalaz
I don't mean go straight ahead all the time, I mean _ONLY_ when the road is clear. If there's no one ahead and the only threats come from behind, the best course if action is to run for it, not try to shake them as if they were in front of you.

It's either a bug or crappy coding. Neither of which good for the game.


Thank you! Finally someone else sees it for what it is.
 
Mightyhalo
offline
Link
 
Originally posted by Hagalaz
You don't get it. Why would you cut if your road to the end zone was clear? Just run full speed ahead!


It's something in the code. The dot knows he is going to be caught so he tries to put himself in a position to run that straight line to the end zone. Low level dots can't make the cut without losing a ton of speed and it ends up hurting them, but it's been this way since I have been here. This is nothing new tbh for lower level dots.
 
manx
offline
Link
 
the tackler was clearly catching up to him, so he tried to do a move to lose him, and since he has no agility, it hurt him. New players do it all the time
 
Tigam
offline
Link
 
Originally posted by uoY_redruM
I don't understand in ounce why you'd say its speed related.

He was not chased down from behind, he STOPPED running more then once which then and only then caused him to get chased down from behind.

I'm saying that I can't help you... And I'm sure there is more than one person chuckling about it.
 
Hagalaz
offline
Link
 
Originally posted by Mightyhalo
It's something in the code. The dot knows he is going to be caught so he tries to put himself in a position to run that straight line to the end zone. Low level dots can't make the cut without losing a ton of speed and it ends up hurting them, but it's been this way since I have been here. This is nothing new tbh for lower level dots.


Old problems are still problems.
 
ryan_grant-25
offline
Link
 
try boosting your KR
 
oldskool
offline
Link
 
[ ] Outrun people you've already outrun
[x] Try to juke them because the sim is secretly trying to run Tecmo Super Bowl and it knows if you run back and forth in a zigzag pattern you can't be caught
 
Hagalaz
offline
Link
 
Hey, I have a better example here. This is my level 20 returner. MVP last season, so he has MVP equipment in agility, speed and change direction. He also has CEQ in the speedster tree, meaning access to change direction and return man, both favored since he is of the returner archetype. His NATURAL agility is above the third cap. Won't say where equipment is placed for obvious reasons. Also, I think I should mention that in an attempt to neutralize our special teams unit, the opponent did not punt at all. Zero punts. Zero. So he had a grand total of... TWO KICK RETURNS, meaning it's not a confidence or stamina issue. Also, not in cruise control mode, since we were only winning by 40ish at the time.

So check out the following.

http://goallineblitz.com/game/replay.pl?game_id=1150241&pbp_id=5045344

I could let the replay speak for itself, but... He stopped SIX times with a clear touchdown in sight. Obviously, no problem here, right ? Working as intended, no bug or crappy coding, right?

I assume multiple examples of this have been posted on the bugs forum, but if not, could someone warn me so I make an appropriate post? Staz/Catch22/mat mcbriar , any of the active people around here, just gimme the flag and I'll make the appropriate post.
Edited by Hagalaz on Apr 12, 2010 00:23:46
Edited by Hagalaz on Apr 11, 2010 22:18:28
Edited by Hagalaz on Apr 11, 2010 22:17:26
 
uoY_redruM
offline
Link
 
Originally posted by Hagalaz
Hey, I have a better example here. This is my level 20 returner. MVP last season, so he has MVP equipment in agility, speed and change direction. He also has CEQ in the speedster tree, meaning access to change direction and return man, both favored since he is of the returner archetype. His NATURAL agility is above the third cap. Won't say where equipment is placed for obvious reasons. Also, I think I should mention that in an attempt to neutralize our special teams unit, the opponent did not punt at all. Zero punts. Zero. So he had a grand total of... TWO KICK RETURNS, meaning it's not a confidence or stamina issue. Also, not in cruise control mode, since we were only winning by 40ish at the time.

So check out the following.

http://goallineblitz.com/game/replay.pl?game_id=1150241&pbp_id=5045344

I could let the replay speak for itself, but... He stopped SIX times with a clear touchdown in sight. Obviously, no problem here, right ? Working as intended, no bug or crappy coding, right?

I assume multiple examples of this have been posted on the bugs forum, but if not, could someone warn me so I make an appropriate post? Staz/Catch22/mat mcbriar , any of the active people around here, just gimme the flag and I'll make the appropriate post.


....wow. Yeah, looks pretty much exactly what happened to my return man. Clear field, should have been a TD without a doubt.
 
Page:
 


You are not logged in. Please log in if you want to post a reply.