http://iscoresports.com/

Having read previous threads about substitutions, I want to be very clear what I'm asking for, and also what I do NOT want to see.

First, what I don't want to see: I don't want to see the flexible form of defensive substitutions go away for the many leagues where batting order rules are relaxed for instructional purposes. I see the great usefulness of that approach, and understand it is essential for many, many users.

Second, what I do want to see: an option to link defensive and offensive substitutions (call it "MLB substitutions" or whatever). A player on this level is in the lineup, or out, but is ineligible to return after his or her appearance is completed. (Rule 3.03 and 3.04). Players can switch positions, but not their spot in the batting order. (The only position that cannot be shifted in the batting order is Designated Hitter as Rule 6.10(b) provides, and iScore appears to provide for that by flagging the "DH Slot" for the game. I'm presuming logic is already present to implement all of 6.10(b)'s provisions.)

From the scorer's perspective, it is inconvenient and cumbersome to make a defensive switch, then tap the "Offense" tab while retaining the name/number of the player who just went out, find their spot in a horizontal batting order designating ONLY number and position, tap it, and then again scroll to the same player who was just substituted in on defense.

It would make more sense from that perspective to tap a preference flag that changes the behavior: substituting in the player on both the field and in the batting order, with one selection. Double switches would still work: you're changing the field position, so you start with the field player that's out, substituting the one who is shifting. The logic can ask if that player is shifting from his/her current position, thus retaining that player's spot in the batting order. Finally, there will be an open field position and an empty spot in the batting order (the player who left); tapping the field position will bring a new player into the game on both defense and offense.

Probably took a minute to read all that, but again I want to be clear about what I am requesting. I'm sure there are improvements that could be made in the logic in the preceding paragraph, but that's the basic algorithm.

Please consider this enhancement as a substantial interface improvement for your users who are scoring MLB and MiLB games.

Thank you for the suggestion. Even in MLB games, as a fan, when you see a different player come to bat, you don't know if that player is pinch hitting, or permanently in the game. If they do happen to be coming in defensively, you don't know the position they will be playing until they take the field. You can guess, but you won't know. The way we have things now, it does not matter. When they are in the field, you make the defensive changes. When they are at bat, you make the offensive changes. All this is done as you see it. No guesswork involved.

We hear and understand your suggestion, and will add it to our list for future prioritization as we continue to enhance iScore.

FTMSupport wrote:Thank you for the suggestion. Even in MLB games, as a fan, when you see a different player come to bat, you don't know if that player is pinch hitting, or permanently in the game. If they do happen to be coming in defensively, you don't know the position they will be playing until they take the field. You can guess, but you won't know. The way we have things now, it does not matter. When they are in the field, you make the defensive changes. When they are at bat, you make the offensive changes. All this is done as you see it. No guesswork involved.

We hear and understand your suggestion, and will add it to our list for future prioritization as we continue to enhance iScore.

Thank you for your quick response!

My suggestion is from the defensive end, and is perhaps just a bit biased by having scored a spring training game yesterday to try out the 4.03 new features (which, in a word, rock! only hardcore scorers will appreciate how thrilled I am that you added a shortcut for pickoff attempts). Almost no pinch-hitting, but the visiting team brought a split squad and was playing eight substituted players in the field by the time the game was done.

I perfectly understand from the pinch-hitter perspective, and I agree that it should be left alone. I wasn't addressing that.

From the defensive perspective, though, a fan in any MLB/MiLB ballpark will know where the defensive substitutions are batting. It is the umpire in chief's duty to announce, or cause to have announced, each substitution (Rules 3.06 and 3.08), and they are further posted on the scoreboard, in lineup order. (Even the crappiest MiLB field has a simple lineup strip that shows the batting order by player number and field position.) On game broadcasts, it depends on the director and announcers, but the standard is to announce the substitute player's spot in the batting order. Radio tends to be better about this, and television tends to be lazy.

So, I'm asking you simply to turn the lens away from pinch-hitting (where the current layout works fine) and toward field substitutions (where the interface needs work for those of us who can't relax enough to just "let batting happen" ).

For the record, I think that iScore Baseball is a well-thought-out product, and has steadily evolved to meet my needs.

Thank you for the feedback. We will keep it in mind as we continue to try and improve.