Quote:
Originally Posted by Kelric
Want to see a team eat $136 million for no reason?
|
Just to make it clear, what version were you using at the time and which version was the league started with?
Quote:
Originally Posted by akw4572
Markus, how about a rule of..........if you sign a player to X amount of money, you can't release them X amount of time, unless there is a CEI. Can that be made an option?
|
Crutch fixes like that leave a bad taste in my mouth. There just might be a legitimate situation out there where something like this, but most likely not to this extent, would happen in real life. Maybe it would be better to resort to a fix like that, but I'd much rather see the AI get smart enough that it just signed a player to a big contract, why on earth would it release him the same day? And then just two weeks after it gave up on the player, whyin the world would it give him another chance by signing him to another big contract so soon?
If you do add a crutch like this, would you say the AI can't release a guy the same day as he signed a contract? Okay, maybe that'd be okay, but how long should they have to wait: a week, a month, a year? What about re-signing them after releasing them, do you wait the same time or different? If that rule is triggered by salary, how much: 1M, 5m, 10M?
I wish I could suggest something smart to maybe fix it, but I've got nothing.
Quote:
Originally Posted by Cryomaniac
How about teams don't release players with CEIs until the end of the season, which is much more realistic.
|
That's better although it doesn't solve the sign and release without a CEI.
Quote:
Originally Posted by CHCfan
Is it still true -- maybe I'm misremembering -- that AI teams don't actually have to pay out contracts to released players?
|
I certainly hope not. I'd test it, but with OOTP9 so close at hand, I'd rather wait and test it.
Quote:
Originally Posted by SittingDuck
I don't know. At this point it's like petting a dead dog.
|
Meaning you're pretty sure this is finally fixed in OOTP9 or you just give up on this bug?