Next update is almost here! Topic

Quote: Originally Posted By tzentmeyer on 10/02/2009
For the draft queue you guys are referring to, the problem has always been how to account for position and salary. You have to assume the user is going to fill the queue imperfectly.

Everyone's used to this model for fantasy, but fantasy doesn't have salary requirements.

Think about it for a few moments and you'll understand the problem.

3 picks remaining. Team has 6 pitchers. Queue has 18 1B at the top. Does it pick 3 consecutive 1B since there are open util spots?




I've been thinking about this in terms of progressive drafts and I'm not sure I'd use, or even like, a tool that allows me to load multiple autopicks.

A single autopick would simply be a list of players in order of preference - they're a pretty common feature of progressive. The draft is scheduled to start in 10 minutes, you pick 6th, you send a proxy with 6 names on it to someone who'll be able to pick for you at your scheduled time.

I don't think, as I owner, I could handle ordering the subsequent contingent picks.

Here are three rookies from 1955 for example - Sandy Koufax, Harmon Killebrew, Herb Score. Whoever I draft with pick one is going to create different needs for pick two. If I draft Koufax I'll probably go for a late-blooming position player with pick 2 - someone like Clete Boyer or Gene Freese. If I draft Killebrew it'd be a late-blooming pitcher - Pedro Ramos, for instance. If I draft Score I'd want someone good now - maybe someone like Billy Klaus.

So I'd be willing to settle for the half-a-loaf single autopick rather than the full loaf of a queueful of multiple autopicks.

10/2/2009 10:02 PM
Smart owners who want to be able to get around the IP limit will be able to do so by drafting guys like Frank Gilmore. So I don't think the limit will be that restrictive, just helpful to prevent newer owners from drafting fatigued teams.
10/2/2009 11:53 PM
Isn't the rule meant to be pretty restrictive? If a rule like this isn't "restrictive", then what's the point of having it?

(Edit: Oh, duh. I guess the point is to protect the noobs, like you said. But consider the implications..)

A separate, less general thought:

Say you have an open league team in Petco. The rules tell you, in effect, that you have to draft a Frank Gilmore or somebody and play with a $79.2 MM payroll against the rest of the league. If you want to disincentivize the use of low-IP stadia, while effectively incentivizing (word of the day) the use of high-IP stadia, that's fine. I wouldn't call that a desirable goal.

The net result is that you weaken Petcoish teams while relatively strengthening others. Come to think of it, wouldn't this also push the pitching/offense balance more toward offense by forcing crappier pitchers onto rosters? Maybe not, overall, because the Gilmore Requirement would leave Petcoish owners with less money to spend on their offense, which brings us back to the beginning of this paragraph. Please do not allow yourself to get caught in an infinite reading loop.

Note: The teams I hate to play most play in low-run, 3B-friendly parks like Petco. I'd benefit from a high floor, which would make these guys spend less on their good players than they normally would, while I draft exactly as many innings and spend exactly as much on pitching as I would have before.

10/3/2009 11:12 AM
This post could not be converted. To view the original post's thread, click here.
10/3/2009 6:45 PM
Quote: Originally Posted By tzentmeyer on 10/02/2009For the draft queue you guys are referring to, the problem has always been how to account for position and salary. You have to assume the user is going to fill the queue imperfectly.

Everyone's used to this model for fantasy, but fantasy doesn't have salary requirements.

Think about it for a few moments and you'll understand the problem.

3 picks remaining. Team has 6 pitchers. Queue has 18 1B at the top. Does it pick 3 consecutive 1B since there are open util spots?

Another scenario: 2 picks remaining with $10M. User needs a starting 3B. Other utility and pitching spots remain open. Top 15 players in list are expensive RP. Then a bunch of 3B. Draft will take top guy in queue, expensive RP. then user is with awful 3B.

Lots of scenarios like these arise once you think about it. If we could count on everyone making perfect lists, it'd be easy to do. But we can't.

If you have ideas, please share.

Thank


For the draft queue you guys are referring to, the problem has always been how to account for position and salary.

Most progressives that I am aware of either do not have a salary cap or the cap is extremely difficult to reach due to the nature of progressives. Salary should not be a large issue in a progressive draft queue as that cap is nearly unreachable.

You have to assume the user is going to fill the queue imperfectly.

You can't idiot prove the world. Yes, users are going to screw things up. They can't help it. You can't stop it. We all know people that can screw up a one-man-parade.

Bottom line (for me anyways), a draft queue of sometype is huge, even a one round, this round only queue would be helpful. Forum proxies are equally as imperfect as an imperfect user error.

10/5/2009 9:59 AM
I'm in two progressives with $100m caps, one with a $120m cap. One of the challenges in those leagues - both of which sim two seasons - is to keep under the cap. If they mean to develop a live draft option for progressive leagues they will have to incorporate something to handle salary limitations.
10/5/2009 3:30 PM
The thing about real life innings pitched on a given team...

Real life teams aren't limited to 25 players plus 2AAA.

The Arizona Diamondbacks had 24 different pitchers this year. Also, of course, WIS only allows pitchers with 25 IP so some of those real life IP cannot be captured in the sim.
10/8/2009 1:24 PM
Quote: Originally Posted By llamanunts on 10/02/2009I wouldn't put a requirement any higher than 1100 IP. If you're in a huge - park, why should you have to draft way too many innings... especially when it's perfectly all right to rely on AAA for low-leverage IP
The best reason to do this is to change the objective of the game from, "How do I win a computer-generated simulation?" to "How do I win a game that looks and feels like real baseball?" Then new owners, read customers, will be more likely to stay and play again. Some not so new customers, too.
10/8/2009 2:05 PM
I think the biggest impact (at least on my teams) might be the adjustment to the +/- plays. I have noticed that currently there is not really that huge a penalty for having terrible range players -- (okay, I always draft HoJo and play him at SS with 40 "-" plays, but usually no errors). I routinely have very successful seasons with lousy fielding range teams -- that may now change.
10/8/2009 2:32 PM
This post could not be converted. To view the original post's thread, click here.
10/8/2009 3:05 PM
Bump for folks to see the huge update that in many peoples mind was screwed up.
7/17/2021 7:25 PM
Can someone please explain what the change in fatigue was all about? I know this is an update from 2009 but I’m just curious how fatigue worked previously. Thanks.
7/18/2021 3:59 PM (edited)
◂ Prev 1234
Next update is almost here! Topic

Search Criteria

Terms of Use Customer Support Privacy Statement

© 1999-2026 WhatIfSports.com, Inc. All rights reserved. WhatIfSports is a trademark of WhatIfSports.com, Inc. SimLeague, SimMatchup and iSimNow are trademarks or registered trademarks of Electronic Arts, Inc. Used under license. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.