But how would this work? Will the FC staff need to create 2 separate modes for the same series?I think it would be better if both are separate. Two different types of competition one which is hands on while one is carefree.
But how would this work? Will the FC staff need to create 2 separate modes for the same series?I think it would be better if both are separate. Two different types of competition one which is hands on while one is carefree.
After giving it a thought, seems like there this can be avoided. Doing the selection process all over again for each match can be cumbersome. Not everyone might be keeping close tabs too on the close times of each match. Might give this another go shortly.But how would this work? Will the FC staff need to create 2 separate modes for the same series?
no idea, I just like the idea of selecting a 15 for whole tournament and playing, I think others might like to play with changing everyday.But how would this work? Will the FC staff need to create 2 separate modes for the same series?
I've not yet set this stone. So depending on the interest I can make it so.I just like the idea of selecting a 15 for whole tournament and playing, I think others might like to play with changing everyday.
I think with changes everyday the scorers will have a hard time too because if they miss a day and people change their squad between scoring they might have hard time tracking unless it's automated.I've not yet set this stone. So depending on the interest I can make it so.
Don't think scorers will need to keep track of user's XI. Scoring will not be automated, all that the scorers will be doing is inputting the player's data (runs, wickets, 4s, 6s etc). They don't need to know what changes a user has done to their team. That will be taken care by the system.people change their squad between scoring they might have hard time tracking unless it's automated
Although would take away the fun of seeing the standings change after every match@asprin what about this, scorers only input the runs/wickets/etc for a player at the end of the series/tournament, while participants can keep subbing players in between matches. We could have pre-fixed substitution windows
That and imagine scoring a T20 league tournament that consists of 50-70 matches in one go.Although would take away the fun of seeing the standings change after every match
No, i meant cumulative scoring. For example, Kohli got 170 runs, was dismissed twice, took three catches and one runout. So all that would be inserted together, not match-by-matchThat and imagine scoring a T20 league tournament that consists of 50-70 matches in one go.
Now that I think of this, I'm unable to think of a way to distribute the points. For example, member xyz had Kohli for 1st and 2nd match but subbed him for the 3rd match - so in this case the system won't know Kohli's score in each of the 3 matches to be able to award points to xyz for only the 1st and 2nd match.No, i meant cumulative scoring. For example, Kohli got 170 runs, was dismissed twice, took three catches and one runout. So all that would be inserted together, not match-by-match
Makes sense. And inserting match-by-match scores at the end of the match eliminates the time save that would come with cumulative scoring, so better to keep the current systemNow that I think of this, I'm unable to think of a way to distribute the points. For example, member xyz had Kohli for 1st and 2nd match but subbed him for the 3rd match - so in this case the system won't know Kohli's score in each of the 3 matches to be able to award points to xyz for only the 1st and 2nd match.
This is fantastic. Previously, a 50 off 45 would have counted 67% more than a 30 off 10 in LOs. Now the boundary points will help even the odds.Since "scoring" is the next part that is up for development, a sneak peak into the ACP to allocate points based on the format being played.
View attachment 272801