• 1 Vote(s) - 1 Average
Defense Editing - Winterball
#1
I think the league could highly benefit from adding a defensive WB. After seeing the defensive edits take place for 2 seasons, I've seen something that I find interesting/left out.

As it stands, if the player's field view ratings are high enough, they'll get bumped up to actually being able to play the position. But what about a player like Efrain Montagu in LF? Based off of Andy's guidelines, LF was not touched and Montagu could still run the risk of being a terrible .819 fielder there. There are many others that have the extra predicted positions according to their amateur stats, but can't truly play the position.

Rather than changing the defensive edit guidelines or going back to fix them, I think adding it as a WB program would be a good idea. Anyone like Montagu's case could get a position they played as an amateur fixed. Also, if adding a position (outside of the edit guidelines) makes sense, then that could be done as well. Some ideas...

- A corner outfielder adding 1B to add versatility.
- Any aging player adding 1B simply because that's a natural progression of moving positions.
- A poor defensive infielder moving to the outfield

Maybe we can even come up with a complete list, so that there is no subjectivity. Specifically on the IF moving to the OF, the player would have to be poor defensively and could not take someone like Eric Lindsay (CIN - Sim #5 2070) and move him to CF as the point of this is to give a player a reasonable position to play and Lindsay already has that.

This would be taking a 3B Jonah Lowell (ARI - Sim #5 2070) type and moving him to LF. Or 2B Sean Volpe (MIL- Sim #5 2070) and moving him to LF or CF. They shouldn't lose much or any range or fielding since they're already solidly below average for their current position as well as the positions they're moving to, but IF to OF should see a drop in arm (-5 sounds fair).

I also think having the option to remove positions would be good idea. If Mogul thinks a player can play a certain position, it may have them there even though we know they're terrible. It's like forcing Jim Thome to play 3B at age 40. Mogul would do that if he still had predicted stats at 3B.

For someone like 3B Damian Saragoza (CLE - Sim #5 2070), having Mogul think he can catch is a negative. He'd be much more useful as just a 1B/3B/LF. This one is pretty simple.

Defensive Winterball

Adding
1. Teams can add 2 positions for players each offseason.
2. New position must be approved by Andy.
3. Any age or overall can be done (majors or minors)
4. There is no maximum per player, just 2 total.
5. Cost is $3M per position.

Removing
1. Teams can remove 3 positions for players each offseason.
2. Any age or overall can be done (majors or minors)
3. There is no maximum per player, just 3 total.
4. Cost is $2M per position.

With this I could remove C for Damian Saragoza and add RF in the same offseason for $5M total. I would then have 1 more addition and 2 more removes if I wanted.

Position Adding List
1. Player has played the position as an amateur.
2. Player has secondary position that matches the defensive editing. (i.e. 1B that can also play LF would be approved for RF)
3. 2B can move to any OF if sub-80 range. (He will have -5 arm and roughly the same range and fielding)
4. 3B can move to LF or RF if sub-80 arm or sub-75 range. (He will have -5 arm and roughly the same range and fielding)
5. SS can move to any OF if sub-70 arm or sub-85 range. (He will have -5 arm and roughly the same range and fielding)
6. Any player can add 1B.
Cle

Cleveland Record5304-4625 (.534) [2054-2071, 2083-2104, 2110-2131]
AL Post: 15 (ALC), 11 (WC) - ALDS Win: 11 - ALCS Champ: 6 - WS Champ: 3

ALW: Mariners + Angels Record: 1072-864 (.554) [2042-2048, 2105-2110]
AL Post: 3 (ALW), 4 (WC) - ALDS Win: 3 - ALCS Champ: 1 - WS Champ: 1

NLW: Rockies + Padres Record: 3230-2753 (.540) [2017-2042, 2072-2082]
NL Post: 18 (NLW), 4 (WC) - NLDS Win: 7 - NLCS Champ: 4 - WS Champ: 0
#2
Bringing this back up. It'd be good to get some conversation going on this. I had a few people message me about this idea when I originally posted it, so I know there's some support on it.
Cle

Cleveland Record5304-4625 (.534) [2054-2071, 2083-2104, 2110-2131]
AL Post: 15 (ALC), 11 (WC) - ALDS Win: 11 - ALCS Champ: 6 - WS Champ: 3

ALW: Mariners + Angels Record: 1072-864 (.554) [2042-2048, 2105-2110]
AL Post: 3 (ALW), 4 (WC) - ALDS Win: 3 - ALCS Champ: 1 - WS Champ: 1

NLW: Rockies + Padres Record: 3230-2753 (.540) [2017-2042, 2072-2082]
NL Post: 18 (NLW), 4 (WC) - NLDS Win: 7 - NLCS Champ: 4 - WS Champ: 0
#3
I'm not necessarily opposed to it, I like it in theory, but I am slightly worried about workload with it. I guess I'm curious to see how often people feel like they would use this.

If it's roughly winterball level participation (50-60% of the league) it's probably doable. But if it's saturated every year than that could be problematic for me. It's time consuming enough processing MLD and draft day contracts.
World Champion 2018, 2021, 2026, 2030, 2035, 2037, 2039
AL Champion 12 times
FCM Best Record-Holder - 121-41 2028
Overall Record: 3530-1978 .641%
#4
I don't see the benefit in potentially removing positions. Even if you keep a guy on the bench, Mogul often times will play them out of position, so keeping predicted stats at those positions seems like something you would always want to do.

I would also up the cost on this to the $5-10 mil range.
Nym GM 2050 - 2070, 2122 - present

Padres co-GM: 2117 - 2121
Cubs co-GM: 2098 - 2101, 2110 - 2116
Royals GM 2085, 2101 - 2110
White Sox GM 2089 - 2091
Expos GM 2071 - 2084
Orioles co-GM 2012 - 2014, GM 2039 - 2050

5 Pennants (2040, 2048, 2051, 2074, 2082)
4 World Championships (2040, 2048, 2051, 2082)
#5
:laa2:

I'm for the idea. As long as it doesn't put to much of a burden on Andy. I think it gives teams the ability to have true utility players on their team. Bc almost every ML team has a guy that can play almost every position. They may not be great at those positions but they can play those positions
« Next Oldest | Next Newest »

Users browsing this thread: 2 Guest(s)



Forum Jump: