i've very sure that such things - which include ROP and QB runs, was addressed by both the community and JDB oh... I want to say 4.3 or 4.4 ish. It was right about the same time hot reads became super rare.

EDIT: Inserts my continued and repeated request to fix the forums search to anything other than the completely unsearchable mess that it is now.
Whew. Let's continue. :)

Anyway, martin is correct. It was posted then that the engine could not handle such plays, and that QB runs/ROP was not able to be done because a) it had been done and was a YUGE problem and b) the game engine can not yet do such things.

The same holds true to this day, as the game engine has yet to become the main focus. It soon will be, though.

It's good to get the nugget that long plays - and other engine issues - are starting to be quietly addressed.

I'd like to suggest to not tweak the current game engine in situ. That uncertainty is unfair to the community.

I'd like to again suggest creating an entirely different server that allows game engine issues and fixes to be fully tested by a community that meets defined testing criteria.
Fixing and testing bugs becomes it's own competition. It really does!

I'd suggest such beta testers of the future game engine to be rewarded for their work.

I'd suggest 1 C level (a full league inc up to 10 AI teams) leagues specifically and only for testing bugs and engine fixes be free to any player that meets defined obligations. Folks that are happy to be told this week you will run this play or only this formation or only long plays or whatever needs data. Meet these goals/test these bugs and fixes or next man up.
Exclusivity guarantees interest.

Accomplishing the above would require what is really needed to be able to address specific engine bugs and fixes - a platform that permits testers to only test the bug or fix. Repeatedly. To be clear: having beta or c leagues will never provide the specific data needed for discovery. Being able to run a specific play against a specific play an infinite amount of times, will. Specify the test, reduce all the collateral and unnecessary data currently obtained by running a beta league.

Testing must be streamlined in order to create an efficient path towards an alpha game engine update. I'm NOT suggesting that.
Beta testing is and should only be for final testing of a product that is near release to the public. Play the new engine before it's released testing.

I appreciate all the work being done by every one involved.
Thank you for all the feedback given to our inquiries.
Change is hard, but we can do it.

MFN-1 is the test league for changes. Game engine changes are run in there, only when looking like a decent change is it then rolled out to other leagues.

From memory, JDB has own test league, able to run high number of simulations before releasing to MFN-1.

As always, roadmap is here.

https://www.myfootballnow.com/roadmap