I use batch load on the website to load team rosters before I see them play.
It's annoying that the website assumes that everybody on the team is batting when you load through batch. I think it should assume "No" for batting.
Thanks!
Ray
Batch load should not assume all players are batting
Re: Batch load should not assume all players are batting
Ray, it would depend on the level of baseball you are scoring. With youth baseball there are 11 or 12 players on a team. If coach is batting continuous lineup then all players bat, often there are at least 10 of the 12 batting. Therefore when you put a batch roster in you do expect the majority of the players to bat. Even if 9 bat that only leaves 2 or 3 to change to batting=no, I would sooner change the 2 or 3 and not the 9. JMO
-
baystatebaseball
- Posts: 43
- Joined: Sun Aug 02, 2009 5:59 pm
Re: Batch load should not assume all players are batting
My kid plays in a league in which teams can have as many as 20 players listed on their official roster, but may only dress 12 per game, and can only bat 9.
This means that -- absent any information about who the starting 9 are on a team -- my worst case is that I have to set 11 imported players to "No" when I get the other team's lineup for a game. While slightly annoying, I haven't found this to be a big burden. On the other hand, if I were to get the other team's lineup moments before the first pitch (which sometimes happens), and didn't have any players set to "Yes", that would cause a bigger burden.
I think the fact that you can set the batting designator on or off on the web site prior to importing -- i.e., the bulk import doesn't assume YES; you can override it to NO on the web site -- gives you the all the flexibility you can expect without actually knowing who will bat.
This means that -- absent any information about who the starting 9 are on a team -- my worst case is that I have to set 11 imported players to "No" when I get the other team's lineup for a game. While slightly annoying, I haven't found this to be a big burden. On the other hand, if I were to get the other team's lineup moments before the first pitch (which sometimes happens), and didn't have any players set to "Yes", that would cause a bigger burden.
I think the fact that you can set the batting designator on or off on the web site prior to importing -- i.e., the bulk import doesn't assume YES; you can override it to NO on the web site -- gives you the all the flexibility you can expect without actually knowing who will bat.