Matrix Games Forums

As long as I have been making plays, I really dont know the answer to this...
See pic below:
1.)What is the purpose of the 'Player Settings' block in motion mode. Is that for simply indicating which player is in motion, when there is 'no' unlimited motion?

I swear, im mad as heck at myself. All this time, I have been unaware that you can grab the red square and move it, which would at least allow you to draw motion similar to how it is in the AFL.

Sheesh! At no point have I EVER thought of just clicking on it to move it? With age comes a low curiosity level I guess.

Don't beat yourself up over it, but if you do tape it and put it on YouTube so we can all get a good laugh [:D]   I figured out you can move it by accident.  I thought I put it there once, so I tried dragging it and "wa-la!" 

Gary, we may have to revoke your coaching license.  [;)]
 
As I recall, I went over moving the "waypoint" dots in the PDS a long time ago in this forum.  That would apply to motion as well.  I didn't call them waypoints though.
 
 
 
 
 
 

That was likely in my pre-playmaking days. At one time it was all uniforms all the time for me.

ORIGINAL: Marauders

Gary, we may have to revoke your coaching license.  [;)]

As I recall, I went over moving the "waypoint" dots in the PDS a long time ago in this forum.  That would apply to motion as well.  I didn't call them waypoints though.

If you really wanna' talk about play design, I know my play works, but my QB either throws it too early to the primary receiver, or when I tell my QB to delay his throw, if there's pressure he gets sacked and the hot receiver gets ignored...

1.)What is the purpose of the 'Player Settings' block in motion mode. Is that for simply indicating which player is in motion, when there is 'no' unlimited motion?

I think that is what "defines" the play as having motion. I had a number of plays that showed "motion: none" in the playbook editor (under mfb-util), even though I had set up a player in motion for that play (I could send them in motion when testing the play). When I went back and added the player to that box, the play then showed "motion: WR" in the editor. That was also what was required for the CPU to use motion for that play.

If you really wanna' talk about play design, I know my play works, but my QB either throws it too early to the primary receiver, or when I tell my QB to delay his throw, if there's pressure he gets sacked and the hot receiver gets ignored...

 
The quarterback's drop, the wait states, the progression, the quarterback's intelligence, the timing of receivers looking for the pass, the routes run, and even the speed of the receivers all play a part.  A play often has to be tweaked in practice to get it right, and then that play may be a little off for teams with vastly different personnel.
 
It would be nice to be able to designate a hot route outside of the progression, so that the hot route's receiver isn't the primary receiver, but that isn't an option at this time.  The AI does take this into consideration though because if the QB is pressured, he'll drop out of the read progression and throw to the first open receiver he finds.  In theory, if one designs a pass play that has the hot route receiver looking for the ball early, but the progression receivers are not, the AI should select the hot route when the QB is pressured.