-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Basketball GM - make rookie contracts more sensible #372
Comments
This is just with the hard cap enabled, right? Because with the default settings, there is a rookie contract scale, similar to the NBA. If there was no rookie contract scale, rookies would probably get pretty huge contracts. That's what happened back in the 90s and led to the creation of the rookie contract scale. |
This was taken with default settings (which has the hard cap enabled). All I can see with regards to rookies is contract length based on the round taken, which is [3,2]. |
Default is hard cap disabled and rookies are automatically signed to rookie scale contracts. Try it in a new league. |
Okay, when I run it in a new league with hard cap disabled the contracts make more sense. I have, for example, a 58 overall making 7.5 million for 3 years. |
Yeah, it would be a good idea to add a separate setting for whether or not to use a rookie contract scale, independent of the hard cap setting. Also would be good to make the rookie contract scale customizable. |
Anyone working on this? |
No, you are welcome to! |
In the NBA, rookie contracts tend to be in the range of .5 - 8 M AAV for a 2-3 year deal. However, if you have a really good rookie enter the draft then they could ask for a lot more than that. For instance, here is an example from a save in 2024:
![image](https://user-images.githubusercontent.com/25538316/112404238-5fa5cc00-8ce6-11eb-9039-185d4ecf6880.png)
What I suggest is to change the contract code so that rookies get lower contracts, as it would not make sense for rookies to make big money without proving themselves, first.
The text was updated successfully, but these errors were encountered: