User Pass
Home Sign Up Contact Log In
Page:
 
thehazyone
NFL Replacement Refs SUCK
offline
Link
 
My elusive HB did pretty well with the off tackle plays in the game he just played. These were two TD runs off of the play, in the 2nd one, the blocking is perfect and opens up a huge hole for him. There were still plenty of plays where he was held to less than 4 yards on the play and given that my RB is level 31 and their average defensive starter was level 27, it seemed about right.

http://goallineblitz.com/game/replay.pl?game_id=153730&pbp_id=1068372

http://goallineblitz.com/game/replay.pl?game_id=153730&pbp_id=1068848
 
Mike Rogers
Lead Tester
offline
Link
 
The first drive of that game is pretty good as a test

4 Off Tackle plays.
13 Yards
4 Yards
1 Yards
2 Yards

And the difference was what the defense was expecting, seems about right to me.


(Also noticed, that the HB is Juking behind the line of scrimage.)

 
lawdawg95
offline
Link
 
Bort

I know I've done my fair share of bitching on this thread, but I appreciate you at least listening to us on this and be willing to at least make considerations.
 
Knicksfan20
offline
Link
 
Originally posted by Bort
Originally posted by Mike Rogers

Like this?
http://goallineblitz.com/game/replay.pl?game_id=164429&pbp_id=1027113

(To be fair thats just horrible Defense, and a poor team Vs a Good team, nothing to do with the HBs speed.)

But there was one thing I did notice, once the Back is outside, the WRs seem to hold blocks for a very long time for their level of blocking???

Now it might be because the level of players going against each other is pretty variable in these last few games.



Yeah, like that.

I think players in general have been holding their blocks too long for a while, ever since the beginning of last season. I've had various updates of toning it down here and there, but we might need more adjustments to it.




I bet that has alot to do with lack of strength, alot of d linemen are stacked with agility/speed...when they get around then they are good, but if they are being blocked, they cant do shit cuz they are overpowered.
 
Kirk Gibson
offline
Link
 
Originally posted by Bort
Originally posted by Sledge

Originally posted by Bort


Run pathing got an update this offseason (as mentioned in my announcement).

It's now a combination of the double-pass algo and new path calculation only every so many ticks instead of each tick, frequency depending on elusive/combo/power settings.

Only change I made to the off tackle play, though, is the short RB pause at the beginning to give the FB time to get moving and get to the hole.


Dont understand why you would need to make the change for the FB Bort. There is no problem with the sim related to the FB. The problem lies in peoples builds of the FB in relation to the speed of the HB.

If a team employees a power fullback then they need to understand the limitation they are under for the Hb rushing. Shrug same goes for a pass recieving TE. If a team starts one then there running game will suffer.

These 2 issues wont be resolved until we can assign players to specific plays.

A player that has a blocking Fb must always be aware of what the Hb is doing with his skill points..The FB an Hb on a team need to communicate. If a FB is late hitting the hole the HB shouldnt be increasing his speed with his points he should be working on other things while the Fb brings up his speed.

This fix kinda smacks of the cookie cutter type variety. Everyones Fb no matter how badly built will be able to perform.



Problem is that the HB is set to follow the FB as a lead blocker on many plays. If the FB is super slow in comparison, he will get ahead of him almost right away and the play will break down every time. If the FB gets 2-3 ticks to get going, the HB will actually have a lead blocker at least for a moment, no matter how quick he is.


I would tread lightly on trying to "help" FBs lead block better and put the responsibility on the players to make sure their Fb has enough speed to stay in front of the HB.
 
Link
 
Yea a FB without vision, speed, and agility should be a bad blocker.
 
dpell
offline
Link
 
I only want to say one thing with regards to blocking on outside plays...

Most GLB WR's are built with no concern for outside blocking and most GLB CB's have zero strength so maybe they should be help up by a decent blocking WR.

My teams have made a point since season 3 of training the blocking and strength on our WR's up to the 20-25 range specifically to help with outside runs. If the average GLB WR (10str/10blk) can hold a block on a CB like that for that long something is wrong, but then again, most GLB CB's have less than 25 strength too. Don't nerf the blocking back just because of bad builds. Make sure a WR with decent blocking (IMO 25 is pretty decent for a WR) is able to be effective in that situation.
Last edited Sep 21, 2008 13:02:38
 
Bort
Admin
offline
Link
 
Originally posted by dpell
I only want to say one thing with regards to blocking on outside plays...

Most GLB WR's are built with no concern for outside blocking and most GLB CB's have zero strength so maybe they should be help up by a decent blocking WR.

My teams have made a point since season 3 of training the blocking and strength on our WR's up to the 20-25 range specifically to help with outside runs. If the average GLB WR (10str/10blk) can hold a block on a CB like that for that long something is wrong, but then again, most GLB CB's have less than 25 strength too. Don't nerf the blocking back just because of bad builds.


Depends on if they are blocking CB's or if they are blocking SS's and LB's. If it's similar skilled CBs, then no problem. If it's 80 str LB's and they have 20 strength and blocking, then there's a problem.
 
Ken1
offline
Link
 
Originally posted by Bort
Originally posted by dpell

I only want to say one thing with regards to blocking on outside plays...

Most GLB WR's are built with no concern for outside blocking and most GLB CB's have zero strength so maybe they should be help up by a decent blocking WR.

My teams have made a point since season 3 of training the blocking and strength on our WR's up to the 20-25 range specifically to help with outside runs. If the average GLB WR (10str/10blk) can hold a block on a CB like that for that long something is wrong, but then again, most GLB CB's have less than 25 strength too. Don't nerf the blocking back just because of bad builds.


Depends on if they are blocking CB's or if they are blocking SS's and LB's. If it's similar skilled CBs, then no problem. If it's 80 str LB's and they have 20 strength and blocking, then there's a problem.


Yeah, one problem even from last year was CB's making tackles too easily.

Part of that was (before pitches got messed up around Game 10) they too often had to make them as LB's couldn't make it outside, but part of it was that they got too many chances to make them and were too good at it. A typical CB might have 30 tackling at what are now pretty high levels.

That's plenty to generally bring down most WR's, but even a balanced back of similar level shouldn't be tackled so easily be such CB's (much less a power back, although a power back on a pitch should have trouble outrunning the LB's-- but if he does or they get blocked, the CB should usually fail to bring him down, whether blocked or not).
 
dpell
offline
Link
 
To some extent I think the pitch should work well in GLB because I've seen the builds of most CB's. Speed/agility/vision with very little tackling or strength. I'm going to guess that the average GLB lvl 30 CB has less than 25 strength and less than 30 tackling. Heck, most CB's I recruited were under 20 in strength and under 25 in tackling.

I have a CB on my roster with less speed than most but he has 40+ tackling and as much strength as most safeties. He's honestly built more like a FS should be built in a game where most FS's are built like CB's. He can be a liability against a team's top WR with 90 speed on the deep balls, but if I know they want to run the ball outside a lot he's my starter in the #2 spot. I haven't noticed him getting held up by blockers, but I haven't paid attention since our post-season scrimmages. I may have to go back and watch my season 5 scrimmages. I'll be very disappointed if he's getting blocked like that.
 
HydrOshocK
offline
Link
 
Thank you for doing the right thing and taking care of this issue before the season kicks off Bort. I was a bit harsh in my comments so I apologize, but I felt that it was very important to stress the frustration over some of these unexpected changes that cause a drastic impact on a team's overall performance. We've always been able adapt and overcome previous changes but this one would've caused several very good teams to completely shift their offensive philosophy and it probably would've been the straw that broke the back.

I'm all for seeing this game progress and get better. My only request is that the drastic changes be tested completely and thoroughly before being rolled out, and some advanced notice given so that we don't have to scramble around looking for answers after we've already paid and set ourselves up with a specific game plan for the season.

Thank you again for fixing this problem.

 
Mike Rogers
Lead Tester
offline
Link
 
Its not a question of if the CB should make the tackle, that seems to be working as intended, (good builds will bad builds wont).

The only slight issue is the length of time a WR (ANY WR) can hold a block on a DB.

At the momnet the block is held as long as the play lasts, which has to be wrong.

I have had several games where I GM on both sides and I know the relative strength/blocking of those facing each other, and the WR will always hold the block for at least 5 secs if the two are equally matched.

In fact the WR can be upto 10 lower in combined strength/blocking vs the CBs Strength and still hold a block for 5 secs.

The issue is any CB with an ounce of football knowledge would know not to engage a WR in a block downfield, especially if told to expect the run.

AS blocking is proving so difficult for Bort to fix to his liking, allowing the CB the chance NOT to be blocked in the first place based on his vision levels would be a quick simple solution.

Having WRs blocking toned down a little would be more effective and simpler still, and would actually end up rewarding those who invested time and training.

Right now you dont need to remotely train blocking for a WR to make and hold a block.

Winding it down a little would leave those who did train it with a slight advantage over those that didnt.

A few ball park figures would be;

Anything between 10-15 Blocking should just make a opposition player path around rather than actually be 'Blocked'. (Requires higher Vision)

Between 15-20 engage a block for a second or soo.

Every 10 above that should double the time the block is held.

That way a WR needs to have 30 blocking to hold a block for 3 seconds or so?

That seems to be fair.

As an example of the issue, the WR in this play has only 9 Blocking and 20 Strength.

http://goallineblitz.com/game/replay.pl?game_id=186833&pbp_id=814691

There really is no way he should engage a block, the CB should just have to run around him.
Last edited Sep 22, 2008 00:15:56
 
jordan274
offline
Link
 
any updates?
Last edited Sep 22, 2008 18:04:41
 
Link
 
Originally posted by Bort
Well, I'll make a few adjustments tonight to see if I can nail down what you're talking about. Defense and blocking shouldn't have been affected by the pathing change, since that code block that I updated is only called when the player has the ball. Maybe the "lead ahead" amount needs some updating or something.


Dude, do you really check the sim on a seperate server before you load the changes? I mean, I watched my TE run 20 yards into the backfield the other day...How could it be things get worse as we go along?
 
Kirk Gibson
offline
Link
 
Originally posted by Mike Rogers
Its not a question of if the CB should make the tackle, that seems to be working as intended, (good builds will bad builds wont).

The only slight issue is the length of time a WR (ANY WR) can hold a block on a DB.

At the momnet the block is held as long as the play lasts, which has to be wrong.

I have had several games where I GM on both sides and I know the relative strength/blocking of those facing each other, and the WR will always hold the block for at least 5 secs if the two are equally matched.

In fact the WR can be upto 10 lower in combined strength/blocking vs the CBs Strength and still hold a block for 5 secs.

The issue is any CB with an ounce of football knowledge would know not to engage a WR in a block downfield, especially if told to expect the run.

AS blocking is proving so difficult for Bort to fix to his liking, allowing the CB the chance NOT to be blocked in the first place based on his vision levels would be a quick simple solution.

Having WRs blocking toned down a little would be more effective and simpler still, and would actually end up rewarding those who invested time and training.

Right now you dont need to remotely train blocking for a WR to make and hold a block.

Winding it down a little would leave those who did train it with a slight advantage over those that didnt.

A few ball park figures would be;

Anything between 10-15 Blocking should just make a opposition player path around rather than actually be 'Blocked'. (Requires higher Vision)

Between 15-20 engage a block for a second or soo.

Every 10 above that should double the time the block is held.

That way a WR needs to have 30 blocking to hold a block for 3 seconds or so?

That seems to be fair.

As an example of the issue, the WR in this play has only 9 Blocking and 20 Strength.

http://goallineblitz.com/game/replay.pl?game_id=186833&pbp_id=814691

There really is no way he should engage a block, the CB should just have to run around him.


While I agree with what your saying I do think the changes shouldn't be this dramatic. I agree if Wr's are going to be solid on sweeps they should earn it by working blk/str but smart or not Cbs cant always break a block or decide whether or not the want to engage a WR on a running play.
 
Page:
 


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