MMA/GA and DA/Mercy look like the two ladder games to watch coming up
Forum > Goal Line Blitz 2 > Vet Ladder Talk 6/17
TDiddy8701
offline
offline
Originally posted by Rob.
Watchable yes, but overall a lame batch of games. Not worthy of a write-up.
yea that was basically what I was trying to say... for the most part, a lot of snoozefests
edit: on second thought, MMA may get destroyed by GA... a similar run-heavy Richmond team hammered them earlier this season. Mercy could beat DA... they have been a bit unlucky this season
Watchable yes, but overall a lame batch of games. Not worthy of a write-up.
yea that was basically what I was trying to say... for the most part, a lot of snoozefests
edit: on second thought, MMA may get destroyed by GA... a similar run-heavy Richmond team hammered them earlier this season. Mercy could beat DA... they have been a bit unlucky this season
Edited by TDiddy8701 on Jun 19, 2015 01:44:26
Edited by TDiddy8701 on Jun 19, 2015 01:37:30
Cuivienen
offline
offline
Originally posted by TDiddy8701
we have the tiebreaker on them right now (apparently SoS?)
That's not how ELO really works.
At this point, it is about having as highly ranked a remaining schedule as possible and beating everyone. That maximizes the amount of ELO you accumulate for the rest of the season in order to move ahead of someone above you in the event that they also do not lose. If they do lose, it is much easier, as they will lose a chunk of ELO and drop down.
The previous schedule does not matter other than it has contributed to your current ELO score, but there is no look back for tie breaking purposes and W-L record isn't important either (other than Ws add to your ELO and Ls take away from it). It's just a raw number and whoever has the highest wins.
we have the tiebreaker on them right now (apparently SoS?)
That's not how ELO really works.
At this point, it is about having as highly ranked a remaining schedule as possible and beating everyone. That maximizes the amount of ELO you accumulate for the rest of the season in order to move ahead of someone above you in the event that they also do not lose. If they do lose, it is much easier, as they will lose a chunk of ELO and drop down.
The previous schedule does not matter other than it has contributed to your current ELO score, but there is no look back for tie breaking purposes and W-L record isn't important either (other than Ws add to your ELO and Ls take away from it). It's just a raw number and whoever has the highest wins.
Galithor
offline
offline
Helps to lose early too. Richmond has the same record as GA. Lost H2H to GA. But GA has a more recent loss.
Irishwhiskey119
offline
offline
Originally posted by Galithor
Helps to lose early too. Richmond has the same record as GA. Lost H2H to GA. But GA has a more recent loss.
Plus Richmond has the best Running Back in the game.
Helps to lose early too. Richmond has the same record as GA. Lost H2H to GA. But GA has a more recent loss.
Plus Richmond has the best Running Back in the game.
Absolut Zero
offline
offline
Originally posted by Xars
First play - situation 3rd and 7: Stop it at Tick 34.5 - before the QB winds up. You only have two receivers past the First Down marker. The FS is closer to WR2 than WR1. WR1 has single outside coverage. Your Pass velocity is too slow to beat the FS on the double team. It's a 25 yard throw at that point.
Second play - situation 3rd and 8: Stop it at Tick 35.5. Same as above basically.
Third play - situation 3rd and 6: Stop it at Tick 33.5. Same as above. CB3 and the MLB are also close enough to WR2 that you could say you are quad-teamed here.
But GLB works with vectors and angles, it's part of their pathing for run defense. All of the defenders are moving in opposite directions of WR2. Does QB target decision not work the same way?
Originally posted by Xars
Quite frankly it's a bad play on Third and Long. You need multiple receivers getting to the First Down marker ASAP. You have 2 out of a potential 5.
But I don't think I should need receivers to get to the first down marker ASAP. The QB can hold onto the ball forever if he wants to, you've only sent 3 at the QB, he's not hurried, he can take his sweet time.
Unless the QB's considers a WR open or not open the moment he passes the first down marker, if they're not open he switches reads and waits for the next guy to pass the first down marker? If that's what happens, sure, not throwing to WR2 makes sense, otherwise I don't get it.
It looks like he decides to unload the ball the moment WR1 crosses the first down line. So maybe that's it.
Originally posted by Xars
What's the Route Tech and Quickness on your WR2? (S* Dane Dawkins)
60 and 80.
First play - situation 3rd and 7: Stop it at Tick 34.5 - before the QB winds up. You only have two receivers past the First Down marker. The FS is closer to WR2 than WR1. WR1 has single outside coverage. Your Pass velocity is too slow to beat the FS on the double team. It's a 25 yard throw at that point.
Second play - situation 3rd and 8: Stop it at Tick 35.5. Same as above basically.
Third play - situation 3rd and 6: Stop it at Tick 33.5. Same as above. CB3 and the MLB are also close enough to WR2 that you could say you are quad-teamed here.
But GLB works with vectors and angles, it's part of their pathing for run defense. All of the defenders are moving in opposite directions of WR2. Does QB target decision not work the same way?
Originally posted by Xars
Quite frankly it's a bad play on Third and Long. You need multiple receivers getting to the First Down marker ASAP. You have 2 out of a potential 5.
But I don't think I should need receivers to get to the first down marker ASAP. The QB can hold onto the ball forever if he wants to, you've only sent 3 at the QB, he's not hurried, he can take his sweet time.
Unless the QB's considers a WR open or not open the moment he passes the first down marker, if they're not open he switches reads and waits for the next guy to pass the first down marker? If that's what happens, sure, not throwing to WR2 makes sense, otherwise I don't get it.
It looks like he decides to unload the ball the moment WR1 crosses the first down line. So maybe that's it.
Originally posted by Xars
What's the Route Tech and Quickness on your WR2? (S* Dane Dawkins)
60 and 80.
Absolut Zero
offline
offline
Originally posted by Xars
HB Wheel - only 2 WRs go deeper than 5 yards. YPA for Vet is 4.14 and YPC is 7.42
Flood Left - only 2 WRs go deeper than 5 yards. YPA for Vet is 4.11 and YPC is 8.01
Both require HB release to become the third option past 5 yards.
They aren't bad plays, but they can certainly be bad play calls in certain situations. On 3rd and 8, over half of the catches won't get you a First Down. Never mind the attempts.
Part of this was due to a tactics mess up. Plays were being called at the wrong time. Haven't gone back to check out where exactly the tactics screwed up, but definitely need to.
http://glb2.warriorgeneral.com/game/replay/194887/2020313
http://glb2.warriorgeneral.com/game/replay/194887/2020653
Given how well the FSM QB lobs deep balls over defenders, both of those above plays could've been touchdowns if WR2 had been targeted. The QB just went to the very last read, really quickly. Far more quickly than he should have given only 3 guys were rushing the QB.
HB Wheel - only 2 WRs go deeper than 5 yards. YPA for Vet is 4.14 and YPC is 7.42
Flood Left - only 2 WRs go deeper than 5 yards. YPA for Vet is 4.11 and YPC is 8.01
Both require HB release to become the third option past 5 yards.
They aren't bad plays, but they can certainly be bad play calls in certain situations. On 3rd and 8, over half of the catches won't get you a First Down. Never mind the attempts.
Part of this was due to a tactics mess up. Plays were being called at the wrong time. Haven't gone back to check out where exactly the tactics screwed up, but definitely need to.
http://glb2.warriorgeneral.com/game/replay/194887/2020313
http://glb2.warriorgeneral.com/game/replay/194887/2020653
Given how well the FSM QB lobs deep balls over defenders, both of those above plays could've been touchdowns if WR2 had been targeted. The QB just went to the very last read, really quickly. Far more quickly than he should have given only 3 guys were rushing the QB.
Cuivienen
offline
offline
Originally posted by Galithor
Helps to lose early too. Richmond has the same record as GA. Lost H2H to GA. But GA has a more recent loss.
Yeah, that has more to do with the new ELO reset. You lose early and nobody has that many ELO points accumulated to exchange. Later in the season, the top teams have a lot more ELO points, and therefore a lot more to give up if they do lose.
But even so, not worth thinking about the past in an ELO system. It is already baked in and it won't change the future. All that maters is how much ELO your opponents have going forward and if you beat them or not.
Helps to lose early too. Richmond has the same record as GA. Lost H2H to GA. But GA has a more recent loss.
Yeah, that has more to do with the new ELO reset. You lose early and nobody has that many ELO points accumulated to exchange. Later in the season, the top teams have a lot more ELO points, and therefore a lot more to give up if they do lose.
But even so, not worth thinking about the past in an ELO system. It is already baked in and it won't change the future. All that maters is how much ELO your opponents have going forward and if you beat them or not.
Cuivienen
offline
offline
Originally posted by Absolut Zero
But GLB works with vectors and angles, it's part of their pathing for run defense. All of the defenders are moving in opposite directions of WR2. Does QB target decision not work the same way?
Can't say, but perhaps it is just a spot check on current position, so the vectors have to play out before the QB either sees or is certain that the receiver is actually open.
Originally posted by Absolut Zero
The QB just went to the very last read, really quickly. Far more quickly than he should have given only 3 guys were rushing the QB.
I don't think it really works that way. At least, the evidence I have seen doesn't indicate that. I think it is more a first past the post system. Basically, say your QB wants an openness score of 50 before he passes the ball. The first receiver to hit that gets thrown to. Doesn't matter if another receiver is at 49 and accelerating rapidly and will be a better option in a few more ticks.
But GLB works with vectors and angles, it's part of their pathing for run defense. All of the defenders are moving in opposite directions of WR2. Does QB target decision not work the same way?
Can't say, but perhaps it is just a spot check on current position, so the vectors have to play out before the QB either sees or is certain that the receiver is actually open.
Originally posted by Absolut Zero
The QB just went to the very last read, really quickly. Far more quickly than he should have given only 3 guys were rushing the QB.
I don't think it really works that way. At least, the evidence I have seen doesn't indicate that. I think it is more a first past the post system. Basically, say your QB wants an openness score of 50 before he passes the ball. The first receiver to hit that gets thrown to. Doesn't matter if another receiver is at 49 and accelerating rapidly and will be a better option in a few more ticks.
bhall43
offline
offline
I dunno trying to explain why a QB makes a decision in a game like this by looking at the sim between 2 different targets is nearly impossible. And it should be.
Rob.
offline
offline
Originally posted by bhall43
I dunno trying to explain why a QB makes a decision in a game like this by looking at the sim between 2 different targets is nearly impossible. And it should be.
Yeah it will make your head spin. If play A consistently produces bad results and play B consistently produces better results than I am going to pick play B. Unfortunately, many play in this game produce poor results.
I dunno trying to explain why a QB makes a decision in a game like this by looking at the sim between 2 different targets is nearly impossible. And it should be.
Yeah it will make your head spin. If play A consistently produces bad results and play B consistently produces better results than I am going to pick play B. Unfortunately, many play in this game produce poor results.
bhall43
offline
offline
Originally posted by Rob.
Yeah it will make your head spin. If play A consistently produces bad results and play B consistently produces better results than I am going to pick play B. Unfortunately, many play in this game produce poor results.
Ya, I mean you can pin point the average results of a play pretty easily among the distances versus certain defenses. But pinpointing the reasons behind the QB making the decision he did in those 3 plays is just gonna make you start overanalyzing every little detail without knowing in full what is provided by the code.
Yeah it will make your head spin. If play A consistently produces bad results and play B consistently produces better results than I am going to pick play B. Unfortunately, many play in this game produce poor results.
Ya, I mean you can pin point the average results of a play pretty easily among the distances versus certain defenses. But pinpointing the reasons behind the QB making the decision he did in those 3 plays is just gonna make you start overanalyzing every little detail without knowing in full what is provided by the code.
What just happened? The Drunks took Richmond to overtime and Damn near forced a tie?
http://glb2.warriorgeneral.com/game/game/195521
GG Raiders. Hell of a defense Drew!
http://glb2.warriorgeneral.com/game/game/195521

GG Raiders. Hell of a defense Drew!

drewd21
offline
offline
Originally posted by Dee.
What just happened? The Drunks took Richmond to overtime and Damn near forced a tie?
http://glb2.warriorgeneral.com/game/game/195521
GG Raiders. Hell of a defense Drew!
Dammit
At work will have to watch it later
What just happened? The Drunks took Richmond to overtime and Damn near forced a tie?
http://glb2.warriorgeneral.com/game/game/195521
GG Raiders. Hell of a defense Drew!
Dammit

At work will have to watch it later
Edited by drewd21 on Jun 20, 2015 12:18:23
You are not logged in. Please log in if you want to post a reply.



























