I'll wait to pull my game plan then. I was going to pull my current game plan for a more vertical offense that I've been putting together notes for.

UPDATE: Scratch that. If 0.4.3 is being released this weekend, I need games to finish my "How to Survive the Passing Game in 0.4.3" guide.

I think it worked well.

This play continues to sum up my feelings on 0.4.3: https://mfn1.myfootballnow.com/watch/8300#1505563

And this: https://mfn1.myfootballnow.com/watch/8300#1505579

But let's not leave out this: https://mfn1.myfootballnow.com/watch/8300#1505592

But on the other hand the downfield, into double coverage, catch over is alive and well: https://mfn1.myfootballnow.com/watch/8300#1505618

But let's not leave out this play: https://beta87.myfootballnow.com/watch/1992#362000

Or this amazing drag route: https://beta87.myfootballnow.com/watch/1992#362025

Or every RB swing pass behind the LOS: https://beta87.myfootballnow.com/watch/1992#362049

Or the phantom knockdowns: https://beta87.myfootballnow.com/watch/1992#362077

Or this complete BS where the RB stops to make a catch: https://beta87.myfootballnow.com/watch/1992#362079

I'm convinced that the people pushing for this to be released to all leagues don't actually watch the games. 0.4.3 does some good things, but it is going to **** a lot of people off because they things that it is bad at, it is REALLY BAD at. Who cares if your QB can read multiple receivers if your RB stops dead 90% of the time after catching a pass when he does catch a pass. Who cares when your QB misses wide open receivers that are <20 yards down field so badly that it looks like he's throwing to someone else. And this happens so regularly that people will realize it is an illogical nerf because some other part of the code is broken. Good luck!

The RB stop on short passes is gone in my games. It's true that some throws a are off.

Yes, there are quite a few very bad logical errors in the beta version that is being worked on and imo it's not quite ready to be released. But it sure is close.

Only so much can go right in one update.. seems like when you fix one bug, a few more pop up that need to be adjusted. The coding seems to be very touchy to say the least. It's been forever since 4.2 was released it feels like.

I say that only the RB falling glitch needs to be addressed but other than that, 4.3 should be released. Or we can keep on finding logical errors in the code and hold off on 4.3 until the end of times

Whatever works best :D

If we don't address the logic problems with downfield accuracy, then the RB bug MUST be fixed. Otherwise, owners are caught in a no win situation where they can't throw downfield consistently, and they can't throw short at all.

I somehow missed this play in my film review - maybe I had given up by then - anyway. What the actual eff happens on this play. If you slow it down and zoom it in, you can actually see the LB MOVE OUT OF THE WAY of the RB instead of attempt to make the tackle even though the LB is in position to make an easy tackle here: https://beta87.myfootballnow.com/watch/1992#362104

The thing everyone is overlooking here is 0.4.2 is stable. It has some definite logical flaws, but people know how to game plan around them and the game works well for most owners. 0.4.3 is ... not.

It's not that the game has logical flaws. It's that JDB hasn't been able to isolate and fix the root logical flaws of the release and has bandaid'ed over them. That doesn't make for a successful release. That means that for every flaw we know about and every bandaid put in place there are at least two more that we don't know about yet. That's how software works. Put an unstable product into production and bad things happen.

I'll support it, and I'll help folks game plan around the problems with it. But it's not a good product for release yet.

Ik this was discussed before, and while it has gotten more realistic, sack numbers seem kinda low to me, since several teams in the league finished with sacks per game totals less than the lowest team total in the NFL past season. Is it just me or was this noted and addressed /resolved?