Quote:
Originally Posted by SkyDog
Heh. It's not easy on the "Very Low" setting, and I've already deleted the "Classic" overnight 130ish season test, though it may be in my Recycle Bin still...
|
Again, this "very low" setting is the center of the latest big discussion at FOBL (which I know you know, of course).
We moved from "low" to "very low" as under low it seemed like players were getting hurt frequently, and this led to more injury-related dev hits than many of us would like. Of course, reducing injuries to "very low" made injuries REALLY rare, which for many made roster management - or really the lack thereof - really, really boring (raising fatigue was given as one possible option for making backups more valuable, but that's an AI issue and doesn't really help with owner participation AND it introduces possible AI..."goofiness")
IMO, injury wear should manifest itself not in dev hits, but in an acceleration of the normal career decline. If the player pool is an interstate where most players get on at the same entrance/onramp and players get off at various exits (until all of them have exited, but have been replaced by new players), think of this as an HOV lane of sorts. A player might still get off at the same exit as before, he just speeds along in the HOV lane and gets there sooner than he ordinarily might have.
I'm thinking of a player like
Chase Utley. As a Phillies fan, I think that intrinsically, Utley is still a damned good player. He hasn't lost all of his talent. The problem is that due to injury, he just can't make it on the field. Sure, he does occasionally, but not nearly as often. And when he does, he isn't always 100%, possibly far from it. So you see some drop in output (he's basically a long-term dtd). Nothing huge, but it's there. You also realize that hey, this guy may not last until 36, 37. He might make it to 34, 35. He may not tank (well, I'm hoping he doesn't), but his dev curve definitely accelerated.