solarkev wrote:I actually don't think that the 2020-22 playbooks project needs to be "fixed". I would not use the work-around that I suggested for this project because it will affect the play calling by the AI QBs. Not acceptable because an important feature of this project was all the work accomplished to get the AI to call plays well. I have used the playbooks in this project and will continue to use them. The minor flaw found in the pre-play buttons can be easily worked around.
That being said, if someone, like Rarebutter maybe, would want to use these playbooks for users only (not AI), and they want to see the correct receiver buttons on the play selection screen, then the fix I suggested will help them. Keep in mind that custom plays often have incorrect playart for some routes in the play selection screen. However, both playart and receiver button labels, are correct when looking at the graphics on the field (using "G" for instance).
If the play selection screen imperfections are important to you, then custom plays can't be used. I personally feel that the advantages of modernizing Madden 08 far outweigh the disadvantages of not being able to use all the features in the play selection screens.
Wait, what? No SolarKev you've misunderstood the issue. The play selection screen receiver buttons are fine, it's the actual on field buttons that Mike and I were talking about. The receiver buttons
are not correct when looking at the graphics on the field. Does your fix not solve that?
Open up the Chiefs playbook in practice mode and select the all pass plays button at the play selection screen. When at the LOS of take a look at the WR buttons of any pass play in that book, then see them change immediately post snap. Here's a visual of the issue for non coach mode players, see Kelce and Smith-Schuster:
- Pre Snap
- EA SPORTS(tm) Madden NFL 08 2_12_2023 5_52_15 PM.png (3.85 MiB) Viewed 3198 times
- Post Snap
- EA SPORTS(tm) Madden NFL 08 2_12_2023 5_52_21 PM.png (3.49 MiB) Viewed 3198 times
This issue effects every offensive playbook in this project to a large degree, that I can confirm 100%. I thought I was being helpful and we had a fix. Guess not. Sorry for the misinformation, there was obviously a misunderstanding.