BZ 3315: Starting pitcher contracts

Toado · 06-10-2009, 12:14 AM

In my custom league, whenever I use the "Make fictional player contracts" function, it gives starting pitchers tiny contracts compared to what they should make. While all the best position players are making somewhere in the $17-20 million range, the top starting pitchers only make $3-7 million. They will also agree to extensions for that same price until spring training starts.

Once spring training begins, their demands change to what they should be. (i.e. The day before spring training started, I had a 4.5 star starting pitcher who wanted an extension that paid $4.1 million annually. One day later, he wanted $18.3 million annually.)

Can this be fixed so that starting pitchers get realistic contracts with the "Make fictional player contracts" command?

Tony M · 06-13-2009, 03:42 PM

Would it be possible for you to zip up your .dat files and FTP them to us as per the instructions in the How To FTP Your Files To Us thread. I have tried this Make Fictional Contracts on a test league and find that both pitchers and batters seem to have the same range of contract values.

Toado · 06-14-2009, 08:31 PM

Ok, so I uploaded Toado.zip.... after further analysis, I've realized that position players also do not have large enough contracts until spring training when you use the "Make Fictional Player Contracts" function (it was just easier to notice with pitchers). Anyway, you'll see that after you fill MLB with fictional players and then give them fictional contracts, the team payrolls generally are between $20 and $60 million. If you simulate up to spring training, and then click "Make Fictional Player Contracts" again, most of the team payrolls will have doubled.
Any idea why fair contracts aren't assigned until spring training?

Nutlaw · 06-22-2009, 06:18 PM

I have logged this issue as BZ 3315. Thanks for reporting it.

06-10-2009, 12:14 AM	#1
Toado Minors (Double A) Join Date: Jun 2006 Posts: 107	BZ 3315: Starting pitcher contracts In my custom league, whenever I use the "Make fictional player contracts" function, it gives starting pitchers tiny contracts compared to what they should make. While all the best position players are making somewhere in the $17-20 million range, the top starting pitchers only make $3-7 million. They will also agree to extensions for that same price until spring training starts. Once spring training begins, their demands change to what they should be. (i.e. The day before spring training started, I had a 4.5 star starting pitcher who wanted an extension that paid $4.1 million annually. One day later, he wanted $18.3 million annually.) Can this be fixed so that starting pitchers get realistic contracts with the "Make fictional player contracts" command? Last edited by Toado; 06-10-2009 at 12:29 AM.

06-13-2009, 03:42 PM	#2
Tony M Global Moderator Join Date: Feb 2006 Location: Here Posts: 6,156	Would it be possible for you to zip up your .dat files and FTP them to us as per the instructions in the How To FTP Your Files To Us thread. I have tried this Make Fictional Contracts on a test league and find that both pitchers and batters seem to have the same range of contract values. __________________ This signature is intentionally blank

06-14-2009, 08:31 PM	#3
Toado Minors (Double A) Join Date: Jun 2006 Posts: 107	Ok, so I uploaded Toado.zip.... after further analysis, I've realized that position players also do not have large enough contracts until spring training when you use the "Make Fictional Player Contracts" function (it was just easier to notice with pitchers). Anyway, you'll see that after you fill MLB with fictional players and then give them fictional contracts, the team payrolls generally are between $20 and $60 million. If you simulate up to spring training, and then click "Make Fictional Player Contracts" again, most of the team payrolls will have doubled. Any idea why fair contracts aren't assigned until spring training?

06-22-2009, 06:18 PM	#4
Nutlaw Hall Of Famer Join Date: Apr 2003 Posts: 9,538	I have logged this issue as BZ 3315. Thanks for reporting it.