User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Goes unblocked on the KR.- NOT A BUG - CLOSED
Page:
 
Time Trial
offline
Link
 
http://www.goallineblitz.com/game/replay.pl?game_id=1928430&pbp_id=3516911

Gets to the blockers before the ball gets to the returner, blockers don't make an attempt.
Edited by Lensar on Feb 14, 2012 12:04:01
Edited by Time Trial on Jan 3, 2012 17:12:25
Edited by IdRatherFlyFish on Jan 3, 2012 07:06:32
 
Link
 
Does seem odd that all three wedge blockers failed a vision check at the exact same time.

We need one more replay from you or someone else before we can call this a bug.

I'll keep an eye out.


Fish
 
Farlig
offline
Link
 
Pretty sure this relates to this...

115: Kickoff coverage unit stops and/or does not pursue the ball. This is not a bug. This is currently coded as Bort intends it to be so we can not call any of these issues bugs. When the kick returner misses the catch on the kickoff, the coverage team will either stop still around the 35 yard line or continue in their lanes until the returner recovers the ball. Which action the coverage team does is dependent on the angle, path, and velocity of the kick, but they currently are acting in a fashion that Bort intends and will not converge on the ball until it is recovered. These issues are not considered Bugs and will be closed as such if posted. They will be recoded down the line, but for now it is working correctly as coded.

... and since the dot is fast enough to also get behind the wedge, the wedge dots can't block the dot. I'm pretty sure the wedge, since they can't move before the returner catches the ball, can't block either. Seems to be how it is currently coded and thus needs to be a suggestion. So my guess, WAI currently.
 
TruthHammer
Lead Bugs Mod
offline
Link
 
I don't think the quote from the "quirks" sticky necessarily applies, since it only mentions the coverage units, but I think you hit the nail on the head here.

Originally posted by Farlig
I'm pretty sure the wedge, since they can't move before the returner catches the ball, can't block either. Seems to be how it is currently coded and thus needs to be a suggestion.


I think there would be other potentially negative consequences to allowing those wedge blockers to move earlier. It also seems like it would be a little unfair, since the coverage teams is forced to stay in their lanes. Usually, that works out better for the return unit, but you just caught an unlucky break here. I'll leave it open to see if the issue is more widespread, but I really think this is working as intended.
 
AngryDragon
offline
Link
 
It seems like something has changed this season. I have noticed that only IN4 and maybe IN1 will stop if they reach a certain point too quickly where as the OU slots keep going. Maybe the code has been changed or maybe something is not working as intended.

Example
http://goallineblitz.com/game/replay.pl?game_id=1894373&pbp_id=3613278
 
Farlig
offline
Link
 
Originally posted by TruthHammer
I don't think the quote from the "quirks" sticky necessarily applies, since it only mentions the coverage units, but I think you hit the nail on the head here.


The quote was mainly there to show why the fact the dot continuing forward isn't a bug. The rest of the explanation was to explain the wedge standing their looking silly
Edited by Farlig on Jan 3, 2012 11:43:59
 
TheGreatPuma
offline
Link
 
Originally posted by AngryDragon
It seems like something has changed this season. I have noticed that only IN4 and maybe IN1 will stop if they reach a certain point too quickly where as the OU slots keep going. Maybe the code has been changed or maybe something is not working as intended.

Example
http://goallineblitz.com/game/replay.pl?game_id=1894373&pbp_id=3613278


When playing with special teams during the pre-season I noticed this and moved my gunners to OU2/5 as those slots seem to be unaffected by the forced stop. The only problem with doing this I've noticed is that the stops will at times run past the return man. I'm unsure if it was doing it last season or not.
Edited by TheGreatPuma on Jan 3, 2012 15:27:23
 
Dr. E
offline
Link
 
I think he means to focus on the fact his wedge guy didn't attempt a block? Looked real odd, like those three in the wedge didn't even know the coverage guy was there.
 
Time Trial
offline
Link
 
Originally posted by Dr. E
I think he means to focus on the fact his wedge guy didn't attempt a block? Looked real odd, like those three in the wedge didn't even know the coverage guy was there.


Yeah, every other player will engage a block. Bort just needs to modify the code to allow a blocker maybe not to move, but to at least engage a block.
 
AngryDragon
offline
Link
 
I am not sure but I agree that the gunner going unblocked is the clear issue. I think somebody explained that they are not coded to begin blocking until the returner fields the ball. Prior to this season gunners would hit a stopping point where they would pause if they reached it before the KR fielded the ball. This season it seems like the interior slots still have this stopping point but the outside slots do not. I believe this is the real issue and am not sure if this is on purpose or a bug.

As a suggestion I would say move the stopping point closer to the returner but not get rid of it. Or we will see a lot more replays added to this thread very soon.
 
darncat
offline
Link
 
Originally posted by Dr. E
I think he means to focus on the fact his wedge guy didn't attempt a block? Looked real odd, like those three in the wedge didn't even know the coverage guy was there.


it happens all the time
 
Dr. E
offline
Link
 
Originally posted by darncat
it happens all the time


Happened once to me, but my Dots are still pretty young, vision checks can go bad pretty easy.
 
IIAMLEGEND
offline
Link
 
BEAST!
 
TruthHammer
Lead Bugs Mod
offline
Link
 
Originally posted by Time Trial
Bort just needs to modify the code to allow a blocker maybe not to move, but to at least engage a block.


It's entirely possible that did happen, but the block was missed. (Though I suspect it was not attempted at all.)

Originally posted by darncat
it happens all the time


Links, please.
 
alindyl
offline
Link
 
Here's one that just happened in a game

http://www.goallineblitz.com/game/replay.pl?game_id=1929455&pbp_id=5261719

Didn't help us much but our attacker was past the BW 1 tick before the ball was caught.
 
Page:
 


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