Nate, I guess it is not that odd what happened 2 seasons ago with you and Paul as we are tied for the lead again after another 15 days have passes. That makes 3 of the 4 sims in which we have been tied...will this continue???
Happy to see the Monarchs return to their rightful spot at the top of the division, although it still looks like this is going to be a dogfight to the end for the two playoff berths.
Congratulations to Seattle Monarch Chad Nelligan, who won the 200th game of his illustrious career in style, with a four-hit shutout. Joseph Macaluso also threw two shutouts this sim as the Monarchs pitching appears to be coming around.
And the league loses another great player for the season in David Kerry. That really sucks, Frank. My sympathies, especially as this was his last year under contract. At least it was the only season-ending injury in the majors this sim.
By the way, just for informational purposes, here are the number of season-ending and career-ending injuries so far this season by level.
ML: 10 (2 of them career-ending) AAA: 6 (1 career-ending) AA: 11 (1 career-ending) A: 11 (0 career ending)
Heck, Houston's AA affiliate has lost SIX players to season-ending injuries. On one team!
So, we've lost, on average, a little more than three players per organization for the season in two months of play. I had decided to keep my mouth shut about injuries, but I'm apparently not very good about sticking to my decisions because I have to say that I still think this is really, really stupid. And I'm saying that on the first sim this year where I haven't lost a player for the season.
Can we agree to lower the injury setting? This is out of control and I know of no one (except Jeremy) who really likes the injury setting.
I vote for dropping the setting down one notch immediately. It's what we have in the OEL and that works just fine; there are still injuries but its not like the MASH units needed here.
OK, seriously: What. The. Hell? The computer keeps starting Frank Osborne, over and over and over and over and over. Here are the starters for every game beginning 5/17:
So, in this stretch of 13 games, the computer has started Osborne (listed as #1) FIVE times. Reuter, my #2, has started once. Hunnicutt, #3, twice. Shipp, #4, twice. Morales, #5, twice. Amell/Lawrence (spot starters), twice total.
What. the. Hell? This is actually a big problem. It's killing - maybe even has killed - my season. Frank Osborne is 0-10. In MAY. He's no doubt exhausted but the computer keeps running him out there and he gets shelled in every start. Alan Reuter's ERA is barely over 2.00 but he can't get a start. And I have no idea how to make it stop.
Seriously, if anyone can figure out what I'm doing wrong, I'd really appreciate it. A lost season is one thing, but when it's because the simulation is wonky like this it's really very frustrating.
We have had these problems before, and they stem from the 7-day lineups. They do not automatically delete the pitcher spot when you put clear lineup after use. Therfore Osborne is listed on that to start often and two consecutive days. You will see that how they are listed is how they have started up on your list of how they started. Just clear out the pitchers from the 7-day lineup and your pitchers will go back to normal. Sorry this happened to you and we should make a regular posting so that all new people know that this will happen.
Frank, it's almost certainly a result of the pitchers you have listed as starting in the seven-day lineups. I strongly advise clearing out the pitchers listed in the seven-day lineups and it should then return to normal. I think.
Every time I've screwed up my lineup or rotation in the past, it's been the seven-day lineup feature that's done it to me. And, the starts you have listed above seem to match the pattern set out in your seven-day lineups (one of the screens available under lineups). As a result of prior self-inflicted misfortunate, I tend to make the settings "NO" for "Use 7-day lineups", "YES" for "allow use of alternative lineup", "YES" for "allow use of depth chart", "YES" for "sit starting pitcher if tired", and "YES" for clear lineup after use. Even with all of the spaces in the lineups underneath clear.
I'm pretty sure my inability to clear out the seven-day lineup feature properly has cost me games in the past. Playoff games too.
Jeremy, I must not be as attentive to the OEL as I thought, because I've clearly missed the time when we proposed lowering the injury setting below "low". Please point me to that discussion, as support for your statement that "the argument is not going to stop with decreasing the level, (every blog in the other league still highlights every injury - so they still care at a 'low' level)."
And, if you can't point me to that discussion, then maybe that means that I mention injuries because injuries are newsworthy and I like to point out newsworthy things in my recaps.
So, if you can't support your statement, then please stop misrepresenting my position, and perhaps the position of others, on injuries. Seriously. Stop it now. It's extraordinarily aggravating to hear you telling me what my beliefs are about the appropriate injury frequency when you consistently have it completely and utterly wrong.
Of course this occurs on Friday night when Zev simply won't be around to see it. But let's see what he has to say about altering the injury level. With Jeremy's abstention I see no actual opposition to the proposal.
Did not mean any offense, earlier comment withdrawn, and I still abstain from the vote. Bring on the fewer injuries...don't think it is going to change much.
Happy to see the Monarchs return to their rightful spot at the top of the division, although it still looks like this is going to be a dogfight to the end for the two playoff berths.
ReplyDeleteCongratulations to Seattle Monarch Chad Nelligan, who won the 200th game of his illustrious career in style, with a four-hit shutout. Joseph Macaluso also threw two shutouts this sim as the Monarchs pitching appears to be coming around.
And the league loses another great player for the season in David Kerry. That really sucks, Frank. My sympathies, especially as this was his last year under contract. At least it was the only season-ending injury in the majors this sim.
By the way, just for informational purposes, here are the number of season-ending and career-ending injuries so far this season by level.
ReplyDeleteML: 10 (2 of them career-ending)
AAA: 6 (1 career-ending)
AA: 11 (1 career-ending)
A: 11 (0 career ending)
Heck, Houston's AA affiliate has lost SIX players to season-ending injuries. On one team!
So, we've lost, on average, a little more than three players per organization for the season in two months of play. I had decided to keep my mouth shut about injuries, but I'm apparently not very good about sticking to my decisions because I have to say that I still think this is really, really stupid. And I'm saying that on the first sim this year where I haven't lost a player for the season.
Can we agree to lower the injury setting? This is out of control and I know of no one (except Jeremy) who really likes the injury setting.
ReplyDeleteI vote for dropping the setting down one notch immediately. It's what we have in the OEL and that works just fine; there are still injuries but its not like the MASH units needed here.
I have to concur with that. It might just be random numbers but this is getting ludicrous.
ReplyDeleteOK, seriously: What. The. Hell? The computer keeps starting Frank Osborne, over and over and over and over and over. Here are the starters for every game beginning 5/17:
ReplyDelete5/17 - Osborne
5/18 - Osborne
5/19 - Hunnicutt
5/21 - Amell*
5/22 - Morales
5/24 - Osborne
5/25 - Osborne
5/26 - Hunnicutt
5/27 - Shipp
5/28 - William Lawrence*
5/29 - Morales
5/30 - Reuter
5/31 - Osborne
* - Listed as a spot starter in my rotation.
So, in this stretch of 13 games, the computer has started Osborne (listed as #1) FIVE times. Reuter, my #2, has started once. Hunnicutt, #3, twice. Shipp, #4, twice. Morales, #5, twice. Amell/Lawrence (spot starters), twice total.
What. the. Hell? This is actually a big problem. It's killing - maybe even has killed - my season. Frank Osborne is 0-10. In MAY. He's no doubt exhausted but the computer keeps running him out there and he gets shelled in every start. Alan Reuter's ERA is barely over 2.00 but he can't get a start. And I have no idea how to make it stop.
Seriously, if anyone can figure out what I'm doing wrong, I'd really appreciate it. A lost season is one thing, but when it's because the simulation is wonky like this it's really very frustrating.
Frank,
ReplyDeleteWe have had these problems before, and they stem from the 7-day lineups. They do not automatically delete the pitcher spot when you put clear lineup after use. Therfore Osborne is listed on that to start often and two consecutive days. You will see that how they are listed is how they have started up on your list of how they started. Just clear out the pitchers from the 7-day lineup and your pitchers will go back to normal. Sorry this happened to you and we should make a regular posting so that all new people know that this will happen.
Frank, it's almost certainly a result of the pitchers you have listed as starting in the seven-day lineups. I strongly advise clearing out the pitchers listed in the seven-day lineups and it should then return to normal. I think.
ReplyDeleteEvery time I've screwed up my lineup or rotation in the past, it's been the seven-day lineup feature that's done it to me. And, the starts you have listed above seem to match the pattern set out in your seven-day lineups (one of the screens available under lineups). As a result of prior self-inflicted misfortunate, I tend to make the settings "NO" for "Use 7-day lineups", "YES" for "allow use of alternative lineup", "YES" for "allow use of depth chart", "YES" for "sit starting pitcher if tired", and "YES" for clear lineup after use. Even with all of the spaces in the lineups underneath clear.
I'm pretty sure my inability to clear out the seven-day lineup feature properly has cost me games in the past. Playoff games too.
By the way, in case anyone is wondering, I'm a vote in favor of tweaking the injury settings down one notch.
ReplyDeleteI know, I know, it's quite a shock to everyone.
I, too, vote in favor of changing the injury frequency setting to "Low".
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteJeremy, I must not be as attentive to the OEL as I thought, because I've clearly missed the time when we proposed lowering the injury setting below "low". Please point me to that discussion, as support for your statement that "the argument is not going to stop with decreasing the level, (every blog in the other league still highlights every injury - so they still care at a 'low' level)."
ReplyDeleteAnd, if you can't point me to that discussion, then maybe that means that I mention injuries because injuries are newsworthy and I like to point out newsworthy things in my recaps.
So, if you can't support your statement, then please stop misrepresenting my position, and perhaps the position of others, on injuries. Seriously. Stop it now. It's extraordinarily aggravating to hear you telling me what my beliefs are about the appropriate injury frequency when you consistently have it completely and utterly wrong.
Rein it in, you two. No sense personalizing it.
ReplyDeleteOf course this occurs on Friday night when Zev simply won't be around to see it. But let's see what he has to say about altering the injury level. With Jeremy's abstention I see no actual opposition to the proposal.
Oh, and Happy Hannukah to you all.
So when is the next sim? Wednesday?
ReplyDeleteDid not mean any offense, earlier comment withdrawn, and I still abstain from the vote. Bring on the fewer injuries...don't think it is going to change much.
ReplyDelete