If you've played Football Mogul for a while, you may have encountered the bug where your starting quarterback tackles the kick returner during a kickoff (?!). Or, worse, your QB is injured during the kickoff (#$%&?!):
Football Mogul 22 introduces the "Playbook Analyzer", a simple but useful tool in the Playbook Editor. Just click any playbook before loading it, and the Playbook Analyzer shows how often each formation is used in that playbook, and calculates the average number of players used at each position.
The first example below shows the "Run + Shoot" offensive playbook, used by teams like the Lions, Oilers and Falcons in the early 1990s. It features 3 or 4 wide receivers on most plays. But unlike many of today's offenses, it doesn't require a highly-rated tight end.
On the right is the "Featured FB" playbook, typified by the 1972 Miami Dolphins, which had 1000-yard rushers at both halfback and fullback.
This feature should make it easier to pick the best playbook for your team. But it should also make it easier to create and manage new custom playbooks.
Knowing that my data was accurate, I created a breakpoint in the debugger to ensure that the data was being loaded correctly — and it was. At this point I just gave up and went to work on other tasks (like the case of the missing pitch). Sometimes your brain just needs a break.
I came back to the Glavine bug over the weekend and saw the same thing: the data was correct and it was being loaded correctly. Then I clicked 'F4' in Excel and the cursor jumped all the way down to line number 90160 where Tom Glavine was listed a second time — but without the 'L' flagging him as a lefty. With a blank data field, Baseball Mogul was giving Glavine the default throwing hand (righty).
I have no idea how this bad data ended up at the bottom of the "master.csv" file (for Glavine and ~8,200 other players whose last names start with 'G'). I get biograhical data from the Baseball Databank, and I guess I grabbed a file that hadn't been finalized yet.
Anyway, Version 24.13 fixes this bug by removing the bad data (although you will need to start a new game to see the changes). Sorry it took so long.
I got an email this week telling me that some pitchers in Baseball Mogul 2021 were losing one or more of their pitches in the off-season. For example, if you start in 1998, Jeff Suppan has 5 pitches. But then this happens at the beginning of 2002:
His cutter disappears, his sinker becomes a slider, and his "four-seamer" becomes a generic "fastball". It turns out that this bug is a side effect of the way we collected pitch data over the years.
In 2016, we added a file called PItch_Type_Frequency.csv, with pitchF/X data going back to the 2002 season. Now, instead of hand-editing each new pitcher's repertoire, I could just update one file. And because I viewed actual pitchF/X data as "better" than the hand-edited file, I told Baseball Mogul to overwrite the data in PitchRatings.csv with data from Pitch_Type_Frequency.csv whenever possible. And this is how Jeff Suppan's pitch repertoire got f---ed up between the 2001 and 2002 season.
It turns out that the hand-edited data had some advantages, such as including 37 different pitch types instead of the 7 tracked by pitchF/X. So I fixed this problem in Version 24.11 by telling Baseball Mogul to prioritize data from the hand-edited file when possible — and to not overwrite a pitcher's pitch repertoire in the middle of their career.
Some Baseball Mogul users are still having problems with McAfee deleting the game after it's been installed. It's been more than 2 years and McAfee still hasn't fixed the known bug in their software.
If you need proof that Baseball Mogul is safe, you can right click on BB-2021.exe and choose 'Scan' (with the red McAfee icon) and McAfee will tell you the program has no viruses. However, whenever you run Baseball Mogul, McAfee deletes it. After fighting with them since 2018, McAfee is still unwilling to fix this bug. So, here are some steps to workaround the problem:
To replace the one file that McAfee keeps deleting, you can get it here (to avoid reinstalling the entire game):
(or http://files.sportsmogul.com/BB-2020.exe for Baseball Mogul 2020)
Copy this file to c:/Sports Mogul/Baseball Mogul 21/ (or wherever you installed the game).
Then you'll have to exclude BB-2021.exe from McAfee's Real-Time Scanning:
1. Run the McAfee program.
2. Click Settings (the circular gear cog) at the top right.
3. Click Real-Time Scanning.
4. Click Excluded Files.
5. Click Add File.
6. Navigate to the location of BB-2021.exe (e.g. C:\Sports Mogul\Baseball Mogul 21)
7. Click 'BB21.exe' and click the 'Open' button.
8. Close McAfee and run Baseball Mogul 2021.
I hope this finally resolves your problem. If not, you probably have a few choices:
1) Go back into McAfee Real-Time Scanning and turn off the entire feature.
2) Contact McAfee product support for help.
3) Uninstall McAfee.
As I said above — and I cannot stress this strongly enough as a small business owner who has been developing virus-free software for more than 20 years — this is McAfee's problem, not ours. Other developers are frustrated by the same bug. We could all use your help in contacting McAfee and stressing to them that this bug is a serious headache for their customers (some of whom have just uninstalled McAfee once they realized that it was constantly deleting a program that McAfee itself verified was virus-free).