Please try and help the Bugs Mods out by giving them the information they need. It doesn't take much to add a brief description to the problem you encountered in a play when you post a pbp link.
For example, let's say you have an issue where the FB goes the wrong way when lead blocking. Post a pbp link and say something along the lines of "the FB is supposed to be lead blocking for the HB here but instead goes and blocks the ROLB across the field." This way when the Bugs Mod looks at the thread, he knows exactly what to look for and can identify an issue.
pbp links with no useful information attached to them will be tagged with NEEDS MORE INFO and not addressed until that information is given.
Originally posted by Catch22 Please try and help the Bugs Mods out by giving them the information they need. It doesn't take much to add a brief description to the problem you encountered in a play when you post a pbp link.
For example, let's say you have an issue where the FB goes the wrong way when lead blocking. Post a pbp link and say something along the lines of "the FB is supposed to be lead blocking for the HB here but instead goes and blocks the ROLB across the field." This way when the Bugs Mod looks at the thread, he knows exactly what to look for and can identify an issue.
pbp links with no useful information attached to them will be tagged with NEEDS MORE INFO and not addressed until that information is given.
You actually need details to see what's wrong here? Took me about 2.5 seconds to see what he was talking about. Now I think I'm going to take a nap.
Actually, doesn't really look like a bug to me... so yes, I need to know why he thinks it's a bug so we can look at exactly what he thinks the issue is and make a determination. The WR was running a streak and reached the end of his route. GLB doesn't have it coded to where routes are adjusted at route end point.
One, is the WR never really reacts to the ball. Not sure if this is a separate build issue or a sim issue as the WR continues to run his route until he is out of the end zone.
Two, is the way the WR stays in the back of the endzone after the INT. Actually the old issue where a player teleports to the middle of the field happens right at the INT. That may be why the WR freezes and never peruses the new ball carrier.
It's pretty obvious catch. the back end-zone line is acting as a barrier. This was going on last season too. Everyone that did not cross the line acted as normal. Everyone that crossed the line got stuck in quick sand.
I believe it was fixed at one time, or it just didn't happen enough to warrant attention from all the testers busy schedules.
If that WR doesn't get stuck and is much faster than the CB...this could be the difference between a TD and a short gain.
Basically a 14 pt turn around. This can't be ignored.
Doesn't look like a bug? Then please explain what they are doing.
I can see after the INT being a bug where the WR and TE just float on the back line. I don't see before then as being a bug.
I'd really like to see more plays similar to this so we can try and figure out exactly what the issue is before sending it to Bort (he would just tell me to get more plays anyway).
Originally posted by Catch22 I can see after the INT being a bug where the WR and TE just float on the back line. I don't see before then as being a bug.
I'd really like to see more plays similar to this so we can try and figure out exactly what the issue is before sending it to Bort (he would just tell me to get more plays anyway).
That's the issue I believe he was talking about. There are plays all the way back from last season on it. He shouldn't need any more.
Sik, both kalk and mine are from the same game/play in case you didn't notice. I'm not sure if there's a number of examples you need before you can make a determination but ours both count as just one.